Payment real-time funds availability

ABSTRACT

A method including receiving a first promise-to-pay message at a second financial institution. The method also can include performing a successful credit for the payment amount to a second account maintained by the second financial institution to make funds available in the second account in real-time after the payment authorization time. The method additionally can include sending a first response from the second financial institution indicating the successful credit of the second account maintained by the second financial institution to inform at least the sender in real-time after the payment authorization time of the successful credit of the second account maintained by the second financial institution. Other embodiments are provided.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. patent applicationSer. No. 14/665,861, filed Mar. 23, 2015. This application also claimsthe benefit of U.S. Provisional Application No. 62/222,773, filed Sep.23, 2015. U.S. patent application Ser. No. 14/665,861 and U.S.Provisional Application No. 62/222,773 are incorporated herein byreference in their entirety.

TECHNICAL FIELD

This disclosure relates generally to financial transaction processing,and relates more particularly to payment real-time funds availability.

BACKGROUND

In conventional payment methods, after a biller sends a bill to acustomer, the customer can initiate a payment to the biller throughvarious different methods, such as through the customer's financialinstitution, a consolidated bill-pay provided, or the biller's financialinstitution, for example. These conventional methods, however, generallydo not allow the biller to have immediate access to the payment funds inreal-time after the customer has initiated the payment to the biller.

BRIEF DESCRIPTION OF THE DRAWINGS

To facilitate further description of the embodiments, the followingdrawings are provided in which:

FIG. 1 illustrates a block diagram of a system that can be employed forreal-time determination of funds availability for check and ACH items,according to an embodiment;

FIG. 2 illustrates an exemplary workflow for real-time determination offunds availability sent from a first financial institution through asystem with a second financial institution determining a paymentlikelihood and without the system making a routing decision, accordingto various embodiments;

FIG. 3 illustrates an exemplary workflow for real-time determination offunds availability sent from the first financial institution of FIG. 2through the system of FIG. 2 with the system of FIG. 2 making a routingdecision of whether to have the second financial institution of FIG. 2determine a payment likelihood, according to various embodiments;

FIG. 4 illustrates an exemplary workflow for real-time determination offunds availability sent from the first financial institution of FIG. 2to the system of FIG. 2 for determining a payment likelihood, accordingto various embodiments;

FIG. 5 illustrates an exemplary flow chart for a method to facilitatedetermining an availability of funds for a payment item, according to anembodiment;

FIG. 6 illustrates an exemplary flow chart for a method to facilitatedetermining an availability of funds for a payment item, according to anembodiment;

FIG. 7 illustrates an exemplary flow chart for a method to facilitatedetermining an availability of funds for a payment item, according to anembodiment;

FIG. 8 illustrates a computer that is suitable for implementing anembodiment of the system of FIG. 1 and/or the system of FIG. 2;

FIG. 9 illustrates a representative block diagram of an example ofelements included in circuit boards inside a chassis of the computer ofFIG. 8;

FIG. 10 illustrates a block diagram of a system in which an applicationservice provider is in data communication with a transaction system, andshowing messages for an “is account real-time capable call,” accordingto an embodiment;

FIG. 11 illustrates a block diagram of the system of FIG. 10, showingpayment messages;

FIG. 12 illustrates a block diagram of a system that is a variation ofthe system of FIG. 10, in which a sending participant of FIG. 10 is indata communication with the application service provider of FIG. 10instead of the transaction system of FIG. 10, and showing the paymentmessages, according to an embodiment;

FIG. 13 illustrates a block diagram of a system that is a variation ofthe system of FIG. 10, showing messages for an “is account real-timecapable call,” according to an embodiment;

FIG. 14 illustrates a block diagram of the system of FIG. 13, showingthe payment messages;

FIG. 15 illustrates a block diagram of a system that is a variation ofthe system of FIG. 10, in which a receiving participant of FIG. 10 is indata communication with the transaction system of FIG. 10 for creditcall messages, and showing messages for an “is account real-time capablecall,” according to an embodiment;

FIG. 16 illustrates a block diagram of the system of FIG. 15, showingthe payment messages;

FIG. 17 illustrates a block diagram of a system that is a variation ofthe system of FIG. 15, in which the receiving participant of FIG. 15 (orFIG. 10) is in data communication for the credit call messages with anapplication service provider of FIG. 15 instead of the transactionsystem of FIG. 15 (or FIG. 10), and showing the payment messages,according to an embodiment;

FIG. 18 illustrates a flow chart for a method to facilitate a real-timefunds availability bill-pay transaction, according to an embodiment;

FIG. 19 illustrates a block of optional first steps, according to theembodiment of FIG. 18;

FIG. 20 illustrates a block of optional second steps, according to theembodiment of FIG. 18;

FIG. 21 illustrates a flow chart for a method to facilitate a real-timefunds availability bill-pay transaction, according to anotherembodiment;

FIG. 22 illustrates a flow chart for a method to facilitate a real-timefunds availability bill-pay transaction, according to anotherembodiment;

FIG. 23 illustrates a block of optional first steps, according to theembodiment of FIG. 22;

FIG. 24 illustrates a flow chart for a method to facilitate a real-timefunds availability bill-pay transaction, according to anotherembodiment;

FIG. 25 illustrates a block of optional first steps, according to theembodiment of FIG. 24;

FIG. 26 illustrates a flow chart for a method to facilitate a real-timefunds availability bill-pay transaction, according to anotherembodiment;

FIG. 27 illustrates a block of optional first steps, according to theembodiment of FIG. 26; and

FIG. 28 illustrates a block diagram of systems that can be employed forfacilitating a real-time funds availability bill-pay transaction.

For simplicity and clarity of illustration, the drawing figuresillustrate the general manner of construction, and descriptions anddetails of well-known features and techniques may be omitted to avoidunnecessarily obscuring the present disclosure. Additionally, elementsin the drawing figures are not necessarily drawn to scale. For example,the dimensions of some of the elements in the figures may be exaggeratedrelative to other elements to help improve understanding of embodimentsof the present disclosure. The same reference numerals in differentfigures denote the same elements.

The terms “first,” “second,” “third,” “fourth,” and the like in thedescription and in the claims, if any, are used for distinguishingbetween similar elements and not necessarily for describing a particularsequential or chronological order. It is to be understood that the termsso used are interchangeable under appropriate circumstances such thatthe embodiments described herein are, for example, capable of operationin sequences other than those illustrated or otherwise described herein.Furthermore, the terms “include,” and “have,” and any variationsthereof, are intended to cover a non-exclusive inclusion, such that aprocess, method, system, article, device, or apparatus that comprises alist of elements is not necessarily limited to those elements, but mayinclude other elements not expressly listed or inherent to such process,method, system, article, device, or apparatus.

The terms “left,” “right,” “front,” “back,” “top,” “bottom,” “over,”“under,” and the like in the description and in the claims, if any, areused for descriptive purposes and not necessarily for describingpermanent relative positions. It is to be understood that the terms soused are interchangeable under appropriate circumstances such that theembodiments of the apparatus, methods, and/or articles of manufacturedescribed herein are, for example, capable of operation in otherorientations than those illustrated or otherwise described herein.

The terms “couple,” “coupled,” “couples,” “coupling,” and the likeshould be broadly understood and refer to connecting two or moreelements mechanically and/or otherwise. Two or more electrical elementsmay be electrically coupled together, but not be mechanically orotherwise coupled together. Coupling may be for any length of time,e.g., permanent or semi-permanent or only for an instant. “Electricalcoupling” and the like should be broadly understood and includeelectrical coupling of all types. The absence of the word “removably,”“removable,” and the like near the word “coupled,” and the like does notmean that the coupling, etc. in question is or is not removable.

As defined herein, two or more elements are “integral” if they arecomprised of the same piece of material. As defined herein, two or moreelements are “non-integral” if each is comprised of a different piece ofmaterial.

As defined herein, “approximately” can, in some embodiments, mean withinplus or minus ten percent of the stated value. In other embodiments,“approximately” can mean within plus or minus five percent of the statedvalue. In further embodiments, “approximately” can mean within plus orminus three percent of the stated value. In yet other embodiments,“approximately” can mean within plus or minus one percent of the statedvalue.

As defined herein, “real-time” can, in some embodiments, be defined withrespect to operations carried out as soon as practically possible uponoccurrence of a triggering event. A triggering event can include receiptof data necessary to execute a task or to otherwise process information.Because of delays inherent in transmission and/or in computing speeds,the term “real-time” encompasses operations that occur in “near”real-time or somewhat delayed from a triggering event. In a number ofembodiments, “real-time” can mean real-time less a time delay forprocessing (e.g., determining) and/or transmitting data. The particulartime delay can vary depending on the type and/or amount of the data, theprocessing speeds of the hardware, the transmission capability of thecommunication hardware, the transmission distance, etc. However, in manyembodiments, the time delay can be less than approximately one second,five seconds, ten seconds, thirty seconds, one minute, or five minutes.

DESCRIPTION OF EXAMPLES OF EMBODIMENTS

Various embodiments include a method to facilitate determining anavailability of funds for a payment item. The method can includeproviding a processing mechanism in data communication through a networkwith a first entity and a plurality of depository financialinstitutions. The plurality of depository financial institutions caninclude a second entity. The method also can include receiving a firstinquiry at the processing mechanism through the network from the firstentity. The first inquiry can be received from the first entity inreal-time after the first entity receives the payment item. The methodfurther can include storing the first inquiry received from the firstentity. The method additionally can include sending a second inquiryfrom the processing mechanism through the network to the second entityin real-time after receiving the first inquiry. The second inquiry canbe based at least in part on the first inquiry. The method further caninclude receiving a first response at the processing mechanism throughthe network from the second entity. The first response can be sent bythe second entity in real-time in response to receiving the secondinquiry. The method additionally can include storing the first responsereceived from the second entity. The method further can include sendinga second response from the processing mechanism through the network tothe first entity in real-time after receiving the first response. Thesecond response can be based at least in part on the first response. Thesecond entity can be specified by the payment item as being responsiblefor paying the payment item. The first entity can be different from thesecond entity. The first and second responses each can include a paymentlikelihood indicator provided by the second entity that indicates alikelihood of the second entity to pay the payment item. The paymentlikelihood indicator can be based at least in part on a current statusand a current available balance of an account maintained by the secondentity that is specified by the payment item for payment of the paymentitem.

A number of embodiments include a system to facilitate determining anavailability of funds for a payment item. The system can include one ormore processing modules in data communication through a network with afirst entity and a plurality of depository financial institutions. Theplurality of depository financial institutions can include a secondentity. The system also can include one or more non-transitory memorystorage modules storing computing instructions configured to run on theone or more processing modules and perform one or more acts. The one ormore acts can include receiving a first inquiry at the processingmechanism through the network from the first entity. The first inquirycan be received from the first entity in real-time after the firstentity receives the payment item. The one or more acts also can includestoring the first inquiry received from the first entity. The one ormore acts additionally can include sending a second inquiry from theprocessing mechanism through the network to the second entity inreal-time after receiving the first inquiry. The second inquiry can bebased at least in part on the first inquiry. The one or more actsfurther can include receiving a first response at the processingmechanism through the network from the second entity. The first responsecan be sent by the second entity in real-time in response to receivingthe second inquiry. The one or more acts additionally can includestoring the first response received from the second entity. The one ormore acts further can include sending a second response from theprocessing mechanism through the network to the first entity inreal-time after receiving the first response. The second response can bebased at least in part on the first response. The second entity can bespecified by the payment item as being responsible for paying thepayment item. The first entity can be different from the second entity.The first and second responses each can include a payment likelihoodindicator provided by the second entity that indicates a likelihood ofthe second entity to pay the payment item. The payment likelihoodindicator can be based at least in part on a current status and acurrent available balance of an account maintained by the second entitythat is specified by the payment item for payment of the payment item.

Some embodiments can include a method to facilitate determining anavailability of funds for a payment item. The method can be implementedvia execution of computer instructions configured to run at one or moreprocessing modules and configured to be stored at one or morenon-transitory memory storage modules. The method can include receivinga first inquiry through a network from a first entity. The first inquirycan be received from the first entity in real-time after the firstentity receives the payment item. the method also can includedetermining a routing decision of whether or not to route the firstinquiry to a second entity. The second entity can be a depositoryfinancial institution that is specified by the payment item asresponsible for paying the payment item. The routing decision can bebased at least in part on a risk of non-payment of the payment item bythe second entity. The method further can include, if the routingdecision is to not route the first inquiry to the second entity, sendinga first response through the network to the first entity in real-timeafter receiving the first inquiry. The method additionally can include,if the routing decision is to route the first inquiry to the secondentity, sending a second inquiry through the network to the secondentity in real-time after receiving the first inquiry. The secondinquiry can be based at least in part on the first inquiry. The methodfurther can include, if the routing decision is to route the firstinquiry to the second entity, receiving a second response through thenetwork from the second entity. The second response can be sent by thesecond entity in real-time in response to receiving the second inquiry.The method additionally can include, if the routing decision is to routethe first inquiry to the second entity, storing the second responsereceived from the second entity. The method further can include, if therouting decision is to route the first inquiry to the second entity,sending a third response through the network to the first entity inreal-time after receiving the second response. The third response can bebased at least in part on the second response. The first entity can bedifferent from the second entity.

Many embodiments can include a system to facilitate determining anavailability of funds for a payment item. The system can include one ormore processing modules in data communication through a network with afirst entity and a second entity. The system also can include one ormore non-transitory memory storage modules storing computinginstructions configured to run on the one or more processing modules andperform one or more acts. The one or more acts can include receiving afirst inquiry through a network from a first entity. The first inquirycan be received from the first entity in real-time after the firstentity receives the payment item. the one or more acts also can includedetermining a routing decision of whether or not to route the firstinquiry to a second entity. The second entity can be a depositoryfinancial institution that is specified by the payment item asresponsible for paying the payment item. The routing decision can bebased at least in part on a risk of non-payment of the payment item bythe second entity. The one or more acts further can include, if therouting decision is to not route the first inquiry to the second entity,sending a first response through the network to the first entity inreal-time after receiving the first inquiry. The one or more actsadditionally can include, if the routing decision is to route the firstinquiry to the second entity, sending a second inquiry through thenetwork to the second entity in real-time after receiving the firstinquiry. The second inquiry can be based at least in part on the firstinquiry. The one or more acts further can include, if the routingdecision is to route the first inquiry to the second entity, receiving asecond response through the network from the second entity. The secondresponse can be sent by the second entity in real-time in response toreceiving the second inquiry. The one or more acts additionally caninclude, if the routing decision is to route the first inquiry to thesecond entity, storing the second response received from the secondentity. The one or more acts further can include, if the routingdecision is to route the first inquiry to the second entity, sending athird response through the network to the first entity in real-timeafter receiving the second response. The third response can be based atleast in part on the second response. The first entity can be differentfrom the second entity.

Further embodiments can include a method to facilitate determining anavailability of funds for a payment item. The method can be implementedvia execution of computer instructions configured to run at one or moreprocessing modules and configured to be stored at one or morenon-transitory memory storage modules. The method can include receivingat least hourly updated account data comprising current statuses andcurrent available balances of accounts maintained by one or moredepository financial institutions. The method also can include receivingan inquiry through a network from a first entity. The inquiry can bereceived from the first entity in real-time after the first entityreceives the payment item. The payment item can specify a second entityas responsible for paying the payment item. The payment item can specifyan account maintained by the second entity for payment of the paymentitem. The one or more depository financial institutions can include thesecond entity. The method additionally can include determining a paymentlikelihood indicator based at least in part on a status and an availablebalance of the account as updated by the updated account data. Thepayment likelihood indicator can indicate a likelihood of the secondentity to pay the payment item. The method further can include storingthe payment likelihood indicator. The method additionally can includesending a response through the network to the first entity in real-timeafter receiving the inquiry. The response can include the paymentlikelihood indicator. The first entity can be different from the secondentity.

In certain embodiments of the method, the payment item can include acheck. The first entity can be a depository financial institutionreceiving the check for deposit. The second entity can be a depositoryfinancial institution against which the check has been drawn.

In certain embodiments of the method, the payment item can include anACH item. The first entity can be an originating depository financialinstitution. The second entity can be a receiving depository financialinstitution. In some embodiments, the first entity can be a processor ora third party acting on behalf of the originating depository financialinstitution. In a number of embodiments, the second entity can be aprocessor or a third party acting on behalf of the receiving depositoryfinancial institution.

In certain embodiments of the method, the inquiry can include a routingnumber of the second entity that is specified by the payment item; anaccount number of the second entity that is specified by the paymentitem; a payment amount that is specified by the payment item; anidentifier of the first entity; a transaction channel identifier thatindicates the channel through which a transacting entity presented thepayment item to the first entity; a payment distribution methodidentifier that indicates how the transacting entity requested to bepaid for the payment item by the first entity; an account number of thefirst entity associated with the transacting entity; and if the paymentitem is a check, a serial number of the check.

In certain embodiments of the method, the payment likelihood indicatorin the response can include an indication of whether or not the secondentity guarantees payment of the payment item.

In certain embodiments of the method, the payment likelihood indicatorin the response can include a score.

In certain embodiments of the method, the response further can includeone or more reason indicators to explain the payment likelihoodindicator.

In certain embodiments of the method, the response can be sent within 30seconds of receiving the inquiry. The payment item can include one of acheck or an ACH item.

Still further embodiments can include a system to facilitate determiningan availability of funds for a payment item. The system can include oneor more processing modules in data communication through a network witha first entity and one or more depository financial institutions. Theone or more depository financial institutions can include a secondentity. The system also can include one or more non-transitory memorystorage modules storing computing instructions configured to run on theone or more processing modules and perform one or more acts. The one ormore acts can include receiving at least hourly updated account datacomprising current statuses and current available balances of accountsmaintained by one or more depository financial institutions. The one ormore acts also can include receiving an inquiry through a network from afirst entity. The inquiry can be received from the first entity inreal-time after the first entity receives the payment item. The paymentitem can specify a second entity as responsible for paying the paymentitem. The payment item can specify an account maintained by the secondentity for payment of the payment item. The one or more depositoryfinancial institutions can include the second entity. The one or moreacts additionally can include determining a payment likelihood indicatorbased at least in part on a status and an available balance of theaccount as updated by the updated account data. The payment likelihoodindicator can indicate a likelihood of the second entity to pay thepayment item. The one or more acts further can include storing thepayment likelihood indicator. The one or more acts additionally caninclude sending a response through the network to the first entity inreal-time after receiving the inquiry. The response can include thepayment likelihood indicator. The first entity can be different from thesecond entity.

In certain embodiments of the system, the payment item can include acheck. The first entity can be a depository financial institutionreceiving the check for deposit. The second entity can be a depositoryfinancial institution against which the check has been drawn.

In certain embodiments of the system, the payment item can include anACH item. The first entity can be an originating depository financialinstitution. The second entity can be a receiving depository financialinstitution.

In certain embodiments of the system, the inquiry can include a routingnumber of the second entity that is specified by the payment item; anaccount number of the second entity that is specified by the paymentitem; a payment amount that is specified by the payment item; anidentifier of the first entity; a transaction channel identifier thatindicates the channel through which a transacting entity presented thepayment item to the first entity; a payment distribution methodidentifier that indicates how the transacting entity requested to bepaid for the payment item by the first entity; an account number of thefirst entity associated with the transacting entity; and if the paymentitem is a check, a serial number of the check.

In certain embodiments of the system, the payment likelihood indicatorin the response can include an indication of whether or not the secondentity guarantees payment of the payment item.

In certain embodiments of the system, the payment likelihood indicatorin the response can include a score.

In certain embodiments of the system, the response further can includeone or more reason indicators to explain the payment likelihoodindicator.

In certain embodiments of the system, the response can be sent within 30seconds of receiving the inquiry. The payment item can include one of acheck or an ACH item.

In various embodiments, a system includes one or more processing modulesand one or more non-transitory memory storage modules storing computinginstructions configured to run on the one or more processing modules andperform certain acts. The acts can include receiving a firstpromise-to-pay message at a transaction system. The first promise-to-paymessage can be based on a successful debit of a first account maintainedby a first financial institution. The successful debit of the firstaccount can be based on a bill payment authorization made by a sender ata payment authorization time. The first account can be held by thesender. The acts also can include storing the first promise-to-paymessage in the transaction system. The acts additionally can includesending a second promise-to-pay message from the transaction system to asecond financial institution. The second promise-to-pay message can bebased on the first promise-to-pay message, such that the secondfinancial institution credits a second account maintained by the secondfinancial institution to make funds available in the second account inreal-time after the payment authorization time. The sender can befinancially liable for the second account. The acts further can includereceiving a first response at the transaction system from the secondfinancial institution indicating a successful credit of the secondaccount maintained by the second financial institution. The actsadditionally can include storing the first response in the transactionsystem. The acts further can include sending a second response from thetransaction system indicating the successful credit of the secondaccount maintained by the second financial institution to inform atleast the sender in real-time after the payment authorization time ofthe successful credit of the second account maintained by the secondfinancial institution. The first financial institution can be differentfrom the second financial institution.

In a number of embodiments, a method can be implemented via execution ofcomputer instructions configured to run at one or more processingmodules and configured to be stored at one or more non-transitory memorystorage modules. The method can include receiving a first promise-to-paymessage at a transaction system. The first promise-to-pay message can bebased on a successful debit of a first account maintained by a firstfinancial institution. The successful debit of the first account can bebased on a bill payment authorization made by a sender at a paymentauthorization time. The first account can be held by the sender. Themethod also can include storing the first promise-to-pay message in thetransaction system. The method additionally can include sending a secondpromise-to-pay message from the transaction system to a second financialinstitution. The second promise-to-pay message can be based on the firstpromise-to-pay message, such that the second financial institutioncredits a second account maintained by the second financial institutionto make funds available in the second account in real-time after thepayment authorization time. The sender can be financially liable for thesecond account. The method further can include receiving a firstresponse at the transaction system from the second financial institutionindicating a successful credit of the second account maintained by thesecond financial institution. The method additionally can includestoring the first response in the transaction system. The method furthercan include sending a second response from the transaction systemindicating the successful credit of the second account maintained by thesecond financial institution to inform at least the sender in real-timeafter the payment authorization time of the successful credit of thesecond account maintained by the second financial institution. The firstfinancial institution can be different from the second financialinstitution.

In various embodiments, a system includes one or more processing modulesand one or more non-transitory memory storage modules storing computinginstructions configured to run on the one or more processing modules andperform certain acts. The acts can include sending a debit message froma transaction system to a first financial institution to debit a firstaccount maintained by the first financial institution based on a billpayment authorization made by a sender at a payment authorization time.The first account can be held by the sender. The acts also can includereceiving a debit response at the transaction system from the firstfinancial institution in real-time after the payment authorization time.The debit response can indicate a successful debit of the first accountmaintained by the first financial institution. The acts additionally caninclude storing the debit response in the transaction system. The actsfurther can include sending a first response to an application serviceprovider indicating the successful debit of the first account maintainedby the first financial institution, such that the application serviceprovider sends a promise-to-pay message to a second financialinstitution to credit a second account maintained by the secondfinancial institution to make funds available in the second account inreal-time after the payment authorization time, and such that theapplication service provider informs the sender in real-time after thepayment authorization time of a successful credit of the second accountmaintained by the second financial institution. The sender can befinancially liable for the second account. The first financialinstitution can be different from the second financial institution. Theapplication service provider can be the same entity as the secondfinancial institution.

In a number of embodiments, a method can be implemented via execution ofcomputer instructions configured to run at one or more processingmodules and configured to be stored at one or more non-transitory memorystorage modules. The method can include sending a debit message from atransaction system to a first financial institution to debit a firstaccount maintained by the first financial institution based on a billpayment authorization made by a sender at a payment authorization time.The first account can be held by the sender. The method also can includereceiving a debit response at the transaction system from the firstfinancial institution in real-time after the payment authorization time.The debit response can indicate a successful debit of the first accountmaintained by the first financial institution. The method additionallycan include storing the debit response in the transaction system. Themethod further can include sending a first response to an applicationservice provider indicating the successful debit of the first accountmaintained by the first financial institution, such that the applicationservice provider sends a promise-to-pay message to a second financialinstitution to credit a second account maintained by the secondfinancial institution to make funds available in the second account inreal-time after the payment authorization time, and such that theapplication service provider informs the sender in real-time after thepayment authorization time of a successful credit of the second accountmaintained by the second financial institution. The sender can befinancially liable for the second account. The first financialinstitution can be different from the second financial institution. Theapplication service provider can be the same entity as the secondfinancial institution.

In various embodiments, a system includes one or more processing modulesand one or more non-transitory memory storage modules storing computinginstructions configured to run on the one or more processing modules andperform certain acts. The acts can include receiving a debit message ata first financial institution to debit a first account maintained by thefirst financial institution based on a bill payment authorization for apayment amount made by a sender at a payment authorization time. Thefirst account can be held by the sender. The acts also can includeperforming a successful debit for the payment amount from the firstaccount maintained by the first financial institution in real-time afterthe payment authorization time. The acts additionally can includesending a debit response from the first financial institution inreal-time after the payment authorization time. The debit response canindicate the successful debit of the first account maintained by thefirst financial institution, such that an application service providersends a first promise-to-pay message for a second financial institutionto credit a second account maintained by the second financialinstitution to make funds available in the second account in real-timeafter the payment authorization time, and such that the applicationservice provider informs the sender in real-time after the paymentauthorization time of a successful credit of the second accountmaintained by the second financial institution. The sender can befinancially liable for the second account. The first financialinstitution can be different from the second financial institution.

In a number of embodiments, a method can be implemented via execution ofcomputer instructions configured to run at one or more processingmodules and configured to be stored at one or more non-transitory memorystorage modules. The method can include receiving a debit message at afirst financial institution to debit a first account maintained by thefirst financial institution based on a bill payment authorization for apayment amount made by a sender at a payment authorization time. Thefirst account can be held by the sender. The method also can includeperforming a successful debit for the payment amount from the firstaccount maintained by the first financial institution in real-time afterthe payment authorization time. The method additionally can includesending a debit response from the first financial institution inreal-time after the payment authorization time. The debit response canindicate the successful debit of the first account maintained by thefirst financial institution, such that an application service providersends a first promise-to-pay message for a second financial institutionto credit a second account maintained by the second financialinstitution to make funds available in the second account in real-timeafter the payment authorization time, and such that the applicationservice provider informs the sender in real-time after the paymentauthorization time of a successful credit of the second accountmaintained by the second financial institution. The sender can befinancially liable for the second account. The first financialinstitution can be different from the second financial institution.

In various embodiments, a system includes one or more processing modulesand one or more non-transitory memory storage modules storing computinginstructions configured to run on the one or more processing modules andperform certain acts. The acts can include providing a paymentapplication to a sender from an application service provider. The actsalso can include receiving a bill payment authorization from the senderthrough the payment application. The bill payment authorization can bemade by the sender at a payment authorization time. The actsadditionally can include sending a first debit message from theapplication service provider to debit a first account maintained by afirst financial institution based on the bill payment authorization. Thefirst account can be held by the sender. The acts further can includereceiving a first debit response at the application service provider inreal-time after the payment authorization time. The debit response canindicated a successful debit of the first account maintained by thefirst financial institution. The acts additionally can includegenerating a first promise-to-pay message for a second financialinstitution to credit a second account maintained by the secondfinancial institution to make funds available in the second account inreal-time after the payment authorization time. The sender can befinancially liable for the second account. The first promise-to-paymessage can be based on the successful debit of the first accountmaintained by the first financial institution. The acts further caninclude sending the first promise-to-pay message. The acts additionallycan include receiving a first response at the application serviceprovider indicating a successful credit of the second account maintainedby the second financial institution. The acts further can includesending a notification to the sender from the application serviceprovider in real-time after the payment authorization time of thesuccessful credit of the second account maintained by the secondfinancial institution. The first financial institution can be differentfrom the second financial institution.

In a number of embodiments, a method can be implemented via execution ofcomputer instructions configured to run at one or more processingmodules and configured to be stored at one or more non-transitory memorystorage modules. The method can include receiving a bill paymentauthorization from the sender through the payment application. The billpayment authorization can be made by the sender at a paymentauthorization time. The acts additionally can include sending a firstdebit message from the application service provider to debit a firstaccount maintained by a first financial institution based on the billpayment authorization. The first account can be held by the sender. Theacts further can include receiving a first debit response at theapplication service provider in real-time after the paymentauthorization time. The debit response can indicated a successful debitof the first account maintained by the first financial institution. Theacts additionally can include generating a first promise-to-pay messagefor a second financial institution to credit a second account maintainedby the second financial institution to make funds available in thesecond account in real-time after the payment authorization time. Thesender can be financially liable for the second account. The firstpromise-to-pay message can be based on the successful debit of the firstaccount maintained by the first financial institution. The acts furthercan include sending the first promise-to-pay message. The actsadditionally can include receiving a first response at the applicationservice provider indicating a successful credit of the second accountmaintained by the second financial institution. The acts further caninclude sending a notification to the sender from the applicationservice provider in real-time after the payment authorization time ofthe successful credit of the second account maintained by the secondfinancial institution. The first financial institution can be differentfrom the second financial institution.

In various embodiments, a system includes one or more processing modulesand one or more non-transitory memory storage modules storing computinginstructions configured to run on the one or more processing modules andperform certain acts. The acts can include receiving a firstpromise-to-pay message at a second financial institution. The firstpromise-to-pay message can be based on a successful debit of a firstaccount maintained by a first financial institution. The successfuldebit of the first account can be based on a bill payment authorizationfor a payment amount made by a sender at a payment authorization time.The first account can be held by the sender. The acts also can includeperforming a successful credit for the payment amount to a secondaccount maintained by the second financial institution to make fundsavailable in the second account in real-time after the paymentauthorization time. The sender can be financially liable for the secondaccount. The acts additionally can include sending a first response fromthe second financial institution indicating the successful credit of thesecond account maintained by the second financial institution to informat least the sender in real-time after the payment authorization time ofthe successful credit of the second account maintained by the secondfinancial institution. The first financial institution can be differentfrom the second financial institution.

In a number of embodiments, a method can be implemented via execution ofcomputer instructions configured to run at one or more processingmodules and configured to be stored at one or more non-transitory memorystorage modules. The method can include receiving a first promise-to-paymessage at a second financial institution. The first promise-to-paymessage can be based on a successful debit of a first account maintainedby a first financial institution. The successful debit of the firstaccount can be based on a bill payment authorization for a paymentamount made by a sender at a payment authorization time. The firstaccount can be held by the sender. The acts also can include performinga successful credit for the payment amount to a second accountmaintained by the second financial institution to make funds availablein the second account in real-time after the payment authorization time.The sender can be financially liable for the second account. The actsadditionally can include sending a first response from the secondfinancial institution indicating the successful credit of the secondaccount maintained by the second financial institution to inform atleast the sender in real-time after the payment authorization time ofthe successful credit of the second account maintained by the secondfinancial institution. The first financial institution can be differentfrom the second financial institution.

In conventional systems, when a first financial institution receives apayment item from a payee, such as a check or an ACH item, to be paidfrom a payor's account maintained by a second financial institution, thefirst financial institution generally does not interact with the secondfinancial institution to determine whether to accept the transactionand/or make the funds for the payment item immediately available to thepayee. Instead, the first financial institution generally makes thatdetermination based on information about the payee, such as the payee'scredit history and/or information about the payee's account(s) (e.g.,account balances) maintained by the first financial institution. In someinstances, the first financial institution may seek information aboutthe payor's account maintained by the second financial institutionthrough a third-party fraud-prevention service, which generally providesinformation about whether the account is open and in good status, hashad recent activity for not-sufficient funds (NSF) or other returnactivity, or had a stop payment order. The fraud-prevention servicegenerally derives this information based on overnight batch datareceived from financial institutions, which in some cases can includethe second financial institution.

Turning to the drawings, FIG. 1 illustrates a block diagram of a system100 that can be employed for real-time determination of fundsavailability for check and ACH items, according to an embodiment. System100 is merely exemplary and embodiments of the system are not limited tothe embodiments presented herein. The system can be employed in manydifferent embodiments or examples not specifically depicted or describedherein. In some embodiments, certain elements or modules of system 100can perform various procedures, processes, and/or activities. In otherembodiments, the procedures, processes, and/or activities can beperformed by other suitable elements or modules of system 100. In someembodiments, system 100 can include a system 110. System 110 can be acomputer system, such as computer system 800, as shown in FIG. 8 anddescribed below, and can each be a single computer, a single server, ora cluster or collection of computers or servers, or a cloud of computersor servers. In several embodiments, system 110 can include a database111. In a number of embodiments, system 110 can include one or moremodules, such as a communications module 112, a data module 113, a riskengine 114, and/or a likelihood calculation engine 115, which aredescribed below in further detail.

In many embodiments, system 110 can be in data communication through anetwork 120 with financial institutions, such as financial institutions131, 132, 133, and/or 134. Network 120 can be the Internet or anothersuitable computer data network. In certain embodiments, each offinancial institutions 131-134 can include a computer system, such ascomputer system 800, as shown in FIG. 8 and described below, and caneach be a single computer, a single server, or a cluster or collectionof computers or servers, or a cloud of computers or servers. In manyembodiments, the financial institutions (e.g., 131-134) can bedepository financial institutions, such as savings banks, credit unions,savings and loan associations, etc. In other embodiments, other forms offinancial institutions and/or other entities can be connected to system110 through network 120.

In a number of embodiments, system 110 can regularly receive informationfrom financial institutions, such as financial institutions 131-134,about accounts maintained by the financial institutions (e.g., 131-134).In various embodiments, the information received from the financialinstitutions can be stored in database 111. For example, in manyembodiments, each of financial institutions (e.g., 131-134) can provideovernight batch data to system 110, which can include information aboutwhether accounts are open and in good status, what balances areavailable in the open accounts, whether accounts have had recent notsufficient funds (NSF) or other activity, and/or whether accounts havehad a stop payment order. In a number of embodiments, system 110 can usethe data provided by the financial institutions to providefraud-prevention services to financial institutions (e.g., 131-134). Forexample, if a payee attempts to cash a check at financial institution131 for a check drawn on a payor's account maintained at financialinstitution 132, financial institution 131 can inquire with system 110about information regarding the payor's account at financial institution132.

In the same or other embodiments, system 110 can provide for interactionbetween the financial institutions (e.g., 131-134). For example, in manyembodiments, system 110 can provide protocols for a financialinstitution (e.g., 131) to communicate with another one of the financialinstitutions (e.g., 132) through system 110 to obtain additionalinformation about whether the other financial institution (e.g., 132)that is specified as responsible for paying a payment item is likely topay the payment item. In some embodiments, the payment item can be acheck. In other embodiments, the payment item can be an ACH item. Forexample, a check can be drawn on an account at the other financialinstitution (e.g., 132), or an ACH item can specific an account at theother financial institution (e.g., 132) for payment, and financialinstitution 132 can be deemed responsible for paying the payment itemusing the specified account. In a number of embodiments, theinteractions between the financial institutions (e.g., 131-134) throughsystem 110 can be limited to inquiries regarding checks or ACH items,and not include inquiries regarding payment card transactions (e.g.,debit card, credit card, etc.). In other embodiments, the interactionsbetween the financial institutions (e.g., 131-134) through system 110can include payment card transactions.

In some embodiments, system 110 can determine whether to route aninquiry from a financial institution (e.g., 131) receiving a paymentitem to another financial institution (e.g., 132) specified by thepayment item as responsible for paying the payment item. Thedetermination can be based on one or more factors, as described below infurther detail. In several embodiments, the financial institution (e.g.,132) that is specified by the payment item as responsible for paying thepayment item can respond with information regarding a likelihood of thatfinancial institution (e.g., 132) paying the payment item. In otherembodiments, information regarding a likelihood of that financialinstitution (e.g., 132) to pay the payment item, such as informationprovided regularly (e.g., twice daily, hourly, half-hourly, on eachtransaction, etc.), can be provided to system 110 by that financialinstitution (e.g., 132). In many embodiments, the financial institution(e.g., 131) that received the payment item can receive the informationregarding the likelihood of payment by the financial institution (e.g.,132) that is specified by the payment item as responsible for paying thepayment item, and can use that information and/or other informationprovided by system 110 to determine whether to approve or deny thetransaction. In many embodiments, system 110 can facilitate real-timedetermination of funds availability on a scale of many financialinstitutions (e.g., greater than 5, 10, 20, 50, 100, 500, 1000, 10,000,or more financial institutions) and can facilitate many suchtransactions (e.g., greater than 100, 1,000, 10,000, 100,000, 1,000,000,10,000,000, or more per day) through system 110.

In certain embodiments, system 110 can provide interaction between thefinancial institutions (e.g., 131-134) for providing credit pushnotifications. For example, in many embodiments, system 110 can provideprotocols for a financial institution (e.g., 131) to communicate withanother one of the financial institutions (e.g., 132) through system 110to notify the other financial institution (e.g., 132) of a credit pushpayment. In some embodiments, for example, a customer can initiatenotification of an ACH credit transaction at financial institution 131(which can be an originating depository financial institution (ODFI)) tocredit an account of a recipient at financial institution 132 (which canbe a receiving depository financial institution (RDFI)), which canresult in a memo post to the account of the recipient at financialinstitution 132 in real-time. In many embodiments, the credit pushtransaction can be cleared through conventional batch processing (e.g.,nightly or interim day batch processing), and the notification can besent from financial institution 131 through system 110 to financialinstitution 132 in real-time, which can beneficially provide financialinstitution 132 with information about future credits to be posted tothe account of the recipient at financial institution 132. In manyembodiments, system 110 can store the transaction, such as in database111. Additional details regarding real-time payment transactions areshown in FIGS. 10-28 and described below.

Turning ahead in the drawings, FIG. 2 illustrates an exemplary workflow200 for real-time determination of funds availability sent from a firstfinancial institution 202 through a system 203 with a second financialinstitution 204 determining a payment likelihood and without system 203making a routing decision, according to various embodiments. Workflow200 is merely exemplary and is not limited to the embodiments presentedherein. Workflow 200 can be employed in many different embodiments orexamples not specifically depicted or described herein. In someembodiments, the procedures, the processes, and/or the activities ofworkflow 200 can be performed in the order presented. In otherembodiments, the procedures, the processes, and/or the activities ofworkflow 200 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of workflow 200 can be combined or skipped. System 203 can besimilar or identical to system 110 (FIG. 1).

In some embodiments, workflow 200 can begin with an activity 211 of anentity, such as consumer 201, presenting a payment item to a firstfinancial institution 202 for a transaction. For example, consumer 201can present a check for $500 to be cashed at a financial institution,such as first financial institution 202. The check can be drawn by apayor against an account of the payor at another financial institution,such as second financial institution 204. In many embodiments, consumer201 can be the payee, endorsee, or bearer of the check. As anotherexample, consumer 201 can make an online purchase at an online retailerby using checking or savings account information for an accountmaintained at a financial institution, such as second financialinstitution 204, and the online retailer can be the originator thatpresents an ACH payment item based on the checking or savings accountinformation to an originating depository financial institution (ODFI).In various embodiments, consumer 201, the originator, and/or the payorcan use the payment item to attempt to effect a transfer of funds (e.g.,make a payment, receive a payment, make a deposit, and/or cash thepayment item) and/or to determine an availability of funds to betransferred using the payment item. For example, the originator canrequest that the ACH payment item be screened through the ODFI.

In many embodiments, workflow 200 can continue with an activity 212 ofthe payment item being received by first financial institution 202. Forexample, first financial institution 202 can receive a physical check orinformation regarding the payment item. For example, the payment itemcan be received through an automated teller machine (ATM), a teller,mail, an online transaction, an online request, remote deposit capture(RDC), lock box, in-store, check processor, or another channel. In otherembodiments, first financial institution 202 can be replaced by theoriginator (such as a merchant) or a payment processor, which caninteract directly with system 203. In some embodiments, first financialinstitution 202 can be a processor or a third party acting on behalf ofthe ODFI. In a number of embodiments, the second entity can be aprocessor or a third party acting on behalf of the RDFI.

In some embodiments, workflow 200 can continue with an activity 213 offirst financial institution 202 determining whether to make an inquiryto system 203 and/or storing the determination. In some embodiments,first financial institution 202 can automatically send an inquiry tosystem 203 after receiving a payment item. In other embodiments, firstfinancial institution 202 can make an internal risk decision based onone or more factors, such as the relationship between first financialinstitution 202 and the requestor (e.g., consumer 201 or the originatorwho provided the payment item to first financial institution 202). Forexample, the requestor can have one or more accounts at first financialinstitution 202. The internal risk decision can be based on the accountbalances of the requestor at first financial institution 202, returnactivity of the requestor at first financial institution 202, a date ofthe payment item, a payment amount of the payment item, and/or arelationship history of deposits of the requestor at first financialinstitution 202. In addition, or alternatively, the internal riskdecision can be based on a relationship history of the payor with firstfinancial institution 202. First financial institution 202 can store theinternal risk decision.

In many embodiments, workflow 200 can continue with an activity 214 offirst financial institution 202 sending an inquiry to system 203, and/orsystem 203 receiving the inquiry from financial institution 202. In anumber of embodiments, the inquiry can be sent from first financialinstitution 202 to system 203 in real-time after activity 212 of firstfinancial institution 202 receiving the payment item. In severalembodiments, the inquiry can include information from the payment itemidentifying the account of the payor, the financial institution (e.g.,second financial institution 204) maintaining the account of the payor,information regarding the requestor, the channel through which therequest was made, the type of transaction, and/or other information. Forexample, in some embodiments, the inquiry can include: (1) the routingnumber (e.g. American Bankers Association (ABA) routing transit number(RTN)) specified by the payment item; (2) the account number specifiedby the payment item; (3) if the payment item is a check, a serial numberof the check; (4) an account transaction (“trans”) code specified by thepayment item; (5) a dollar amount specified by the payment item; (6) anidentifier for the originator, requestor, and/or first financialinstitution 202; (7) one or more channel indicators (e.g., ATM, ateller, mail, an online transaction, the identity of the online device,the location of the online device, RDC, lock box, in-store, checkprocessor, and/or another channel); (8) an identifier of what therequestor has requested with the transaction (e.g., cash, deposit, orpayment); (9) an identifier of the type (e.g., check, ACH item, Standardfor Financial Services Messaging (ISO (International Organization forStandardization) 20022), certified check, payment cards (debit card,credit card), etc.); (10) transaction identifier (ID) or sequence numberfor the transaction (which can be generated by system 203); (11) anaccount number of the requestor, payee, and/or depositor; and/or othersuitable information. For example, in some embodiments, the inquiry caninclude a debit card number for a debit card associated with the accountof the payor. In some embodiments, the debit card number can be includedin the inquiry in lieu of the routing number and/or the account number.In a number of embodiments, the inquiry can include a transactionbusiness date. In certain embodiments, the inquiry can include a primaryclient ID or other ID, a transaction ID, and/or an item ID for thepayment item.

In certain embodiments, the inquiry can include an identifier linked tothe account of the payor. In some embodiments, an identifier can beincluded in the inquiry in lieu of the routing number and/or the accountnumber. For example, the identifier can include a tokenized or maskedtoken, which can be an identifier which can be linked to the account ofthe payor. In some embodiments, the token can be a temporary (e.g.,one-time use, or limited-time use) identifier. In a number ofembodiments, the token include an encrypted identifier. In someembodiments, the identifier in the inquiry can include an email addressof the payor, a phone number of the payor, a device ID of the payor, thename of the payor, a debit card number of the payor, a transactionbusiness date, a transaction ID, an item ID, and/or a client ID. In anumber of embodiments, such as when the account number and/or routingnumber is tokenized, the inquiry can include a tokenized service managerID.

In many embodiments, workflow 200 can continue with an activity 215 ofsystem 203 storing the inquiry sent from first financial institution202. The inquiry can be stored in database 111 (FIG. 1), and can includea timestamp of when the inquiry was received at system 203. In someembodiments when the inquiry includes an identifier, system 203 candetermine the account number and/or routing number from the identifier.

In many embodiments, workflow 200 can continue with an activity 216 ofsystem 203 sending an inquiry to second financial institution 204,and/or second financial institution 204 receiving the inquiry fromsystem 203. In a number of embodiments, the inquiry can be sent fromsystem 203 to second financial institution 204 in real-time afteractivity 214 of system 203 receiving the inquiry. In many embodiments,the inquiry sent to second financial institution 204 in activity 216 canbe similar or identical to the inquiry received by system 203 inactivity 214. In some embodiments, such as when the inquiry of activity214 includes an identifier, the inquiry of activity 216 can include theaccount number and/or routing number from the identifier. In otherembodiments, activity 216 can include the identifier in lieu of theaccount number and/or routing number, and second financial institution204 can determine the account number and/or routing number from theidentifier.

In several embodiments, workflow 200 can continue with an activity 217of second financial institution 204 determining and/or saving a paymentlikelihood. In various embodiments, determining the payment likelihoodcan be based at least in part on current information of the payor'saccount maintained by second financial institution 204 and/orinformation provided to second financial institution 204 in the inquiry.In many embodiments, the financial institutions (e.g., second financialinstitution 204) that participate in services offered through system 203and provide payment likelihood for real-time determination of fundsavailability can have agreed to common consortium rules to be used whendetermining a payment likelihood. The common consortium rules canadvantageously provide consistency across determinations made andinformation provided by different financial institutions. In someembodiments, the providers of system 203 can dictate the consortiumrules to the financial institutions (e.g., second financial institution204) that provide payment likelihood information.

In several embodiments, the consortium rules can address informationthat an inquirer (e.g., first financial institution 202) might want toknow in determining whether to approve or deny a transaction, such ascurrent account status and sufficiency of funds to cover the paymentitem, risk of fraud, money laundering, and/or other factors. Secondfinancial institution 204, which is specified as responsible for payingthe payment item, can beneficially have current detailed informationregarding the payor and/or the payor's account maintained by secondfinancial institution 204. For example, in some embodiments, activity217 of second financial institution 204 determining the paymentlikelihood can be based on one or more rules, such as: (1) determiningwhether the payor's account is currently open (e.g., based on intra-daystatus, if the account is opened or closed during the day of theinquiry); (2) determining whether the current balance and/or availablebalance (e.g., the current balance adjusted by pending transactions thathave not yet cleared) of the payor's account is greater than the amountspecified by the payment item (e.g., is greater than or equal to thepayment amount, is greater than the payment amount by a predeterminedamount (e.g., is the balance at least $200 greater than the paymentamount), or is greater than the payment amount by a factor of thepayment amount (e.g. is the balance at least 150% of the paymentamount)); (3) determining whether the payment amount is in a range ofhistorical spending amounts by the payor (e.g., determining whether thepayment amount is consistent with the payor's spending habits); (4)determining whether there is a likelihood of a deposit to be made intothe account (e.g., on the day of the inquiry) that would make thepayor's account able to cover the payment item, or expected withdrawalsthat would make the payor's account unable to cover the payment item;(5) determining whether the payment item is consistent with a pattern,if any, between the payee and the payor; (6) determining whether otherpayment items have been drawn on and/or presented for clearing againstthe payor's account (e.g., other pending charges) that would affectwhether the payor's account could cover the payment item; (7)determining whether there is a risk of fraud based on activity thatmatches a fraudulent pattern or is inconsistent with the payor'sspending habits; (8) determining whether there is a risk of fraud basedon how recently the payor's account was opened; (9) determining whetherthere is a risk of fraud based on the channel used to present thepayment; (10) determining whether there is a likelihood of moneylaundering based on transaction payment amounts, and/or the identitiesof the payor and/or payee; (11) if the payment item is a check,determining if the account is uses the Positive Pay verificationservice, and if so, verifying that the check is on the list provided bythe payor and if the check has already been paid; (12) if the paymentitem is a check, determining whether the serial number of the check isin pattern (e.g., whether the serial number of the check is not withinthe range of serial numbers in one or more checkbooks that have beenused recently for the payor's account); (13) if the payment item is acheck, determining whether the check is a duplicate of an already-paidcheck; (14) if the payment item is a check, determining whether thecheck is likely a counterfeit, such as based on a statistical analysis;and/or other suitable rules.

In a number of embodiments, the rules can be used to determine alikelihood of whether or not the payment item will clear the payor'saccount at second financial institution 204. For example, in someembodiments, second financial institution 204 can determine a paymentlikelihood indicator, which can be whether or not second financialinstitution 204 guarantees payment of the payment item (e.g., eitherguarantees payment or does not guarantee payment) or whether or notsecond financial 204 is likely to pay the payment item (e.g., either islikely to pay or is not likely to pay). In the same or otherembodiments, second financial institution 204 can determine a paymentlikelihood score, and the payment likelihood indicator can include thepayment likelihood score. In some embodiments, the payment likelihoodscore can be a numeric score (e.g., 0-100), an alphabetic score (e.g.,A-Z), a color score (e.g., red, yellow, or green), or another suitabletype of score. In some embodiments, the payment likelihood indicator caninclude an expiration date/time. For example, the guarantee can have anexpiration date/time after which the guarantee or payment likelihoodindicator will expire.

In a number of embodiments, the payment likelihood indicator can includereason indicators (e.g., reason codes, explanations, attributes, etc.)that explain the reasons for the payment likelihood indicator. Forexample, the reasons can include: (1) that the payment item is not foundon Positive Pay; (2) that the item is a possible duplicate; (3) that theaccount is closed; (4) that there has been fraud or the payment item islikely to be fraud on the account; (5) that the payment item is likelyto be a counterfeit; (6) that the payment amount specified by thepayment item is greater than the current and/or available balance of thepayor's account; (6) that the payor's account is overdrawn or has an NSFstatus; (7) that the account has a sufficient balance; (8) that paymentitem is or is not in pattern (e.g., payment amount is consistent withtransaction history, that the serial number is in the range of serialnumbers in one or more checkbooks that have been used recently for thepayor's account, etc.); (9) that the expected balance is or is notsufficient, based on expected deposits and/or payments; (10) that thepayment is or is not in pattern for transactions between the payor andthe payee; (11) that the item is on Positive Pay and is verified; and/orother suitable reasons.

In many embodiments, workflow 200 can continue with an activity 218 ofsecond financial institution 204 sending a response to system 203,and/or system 203 receiving the response from second financialinstitution 204. In a number of embodiments, the response can be sentfrom second financial institution 204 to system 203 in real-time afteractivity 216 of second financial institution 204 receiving the inquiry.In several embodiments, the response can include the payment likelihoodindicator that was determined in activity 217. In some embodiments, theresponse can include information from the inquiry and/or informationdetermined by second financial institution 204. For example, in a numberof embodiments, the response can include: (1) the routing number (e.g.ABA RTN) specified by the payment item; (2) the account number specifiedby the payment item; (3) if the payment item is a check, a serial numberof the check; (4) an account transaction (“trans”) code specified by thepayment item; (5) a dollar amount specified by the payment item; (6) anidentifier for the originator, requestor, and/or first financialinstitution 202; (7) one or more channel indicators (e.g., ATM, ateller, mail, an online transaction, the identity of the online device,the location of the online device, RDC, lock box, in-store, checkprocessor, and/or another channel); (8) an identifier of what therequestor has requested with the transaction (e.g., cash, deposit, orpayment); (9) an identifier of the type (e.g., check, ACH item, Standardfor Financial Services Messaging (ISO (International Organization forStandardization) 20022), certified check, payment cards (debit card,credit card), etc.); (10) transaction identifier (ID) or sequence numberfor the transaction (which can be generated by system 203); (11) theaccount number of the requestor, payee, and/or depositor; (12) the dateand/or time(s) of the inquiry/inquiries (e.g., based on the timestampstored in activity 215 and/or the time the determination of the paymentlikelihood in activity 217); (13) the payment likelihood indicator(e.g., whether or not guaranteed to pay (which can include a guaranteeexpiration date/time), whether or not likely to pay; and/or the paymentlikelihood score); (14) the reason indicators for the payment likelihoodindicator; and/or other suitable information.

In many embodiments, workflow 200 can continue with an activity 219 ofsystem 203 storing the response sent from second financial institution204 in activity 218. The inquiry can be stored in database 111 (FIG. 1),and can include a timestamp of when the response was received at system203.

In some embodiments, workflow 200 can continue with an activity 220 ofsystem 203 sending a response to first financial institution 202, and/orfirst financial institution 202 receiving the response from system 203.In a number of embodiments, the response can be sent from system 203 tofirst financial institution 202 in real-time after activity 218 ofsystem 203 receiving the response. In many embodiments, the responsesent to first financial institution 202 in activity 220 can be similaror identical to the response received by system 203 in activity 218.

In several embodiments, workflow 200 can continue with an activity 221of first financial institution 202 determining whether to approve ordeny the transaction, actually approving or denying the transaction,storing the approval or denial, and/or notifying consumer 201 of suchapproval or denial. In various embodiments, first financial institution202 can determine whether to approve or deny the transaction based atleast in part on the response received by first financial institution202 in activity 220. By incorporating insight from second financialinstitution 204, first financial institution 202 can advantageously makea more informed decision in determining the availability of funds forthe payment item and in determining whether to approve or deny thetransaction. For example, if the response includes a guarantee ofpayment or an indication or likelihood of payment by second financialinstitution 204, first financial institution 202 can approve thetransaction. If the response includes the payment likelihood score,first financial institution 202 can determine whether the scoreindicates a low enough risk that first financial institution 202 can becomfortable with the risk of approving the transaction.

Turning ahead in the drawings, FIG. 3 illustrates an exemplary workflow300 for real-time determination of funds availability sent from firstfinancial institution 202 through system 203 with system 203 making arouting decision of whether to have second financial institution 204determine a payment likelihood, according to various embodiments.Workflow 300 is merely exemplary and is not limited to the embodimentspresented herein. Workflow 300 can be employed in many differentembodiments or examples not specifically depicted or described herein.In some embodiments, the procedures, the processes, and/or theactivities of workflow 300 can be performed in the order presented. Inother embodiments, the procedures, the processes, and/or the activitiesof workflow 300 can be performed in any suitable order. In still otherembodiments, one or more of the procedures, the processes, and/or theactivities of workflow 300 can be combined or skipped. Workflow 300 canbe similar to workflow 200 (FIG. 2), and various activities of workflow300 can be similar or identical to various activity of workflow 200(FIG. 2).

In some embodiments, workflow 300 can begin with an activity 311 of anentity, such as consumer 201, presenting a payment item for atransaction. Activity 311 can be similar or identical to activity 211(FIG. 2).

In many embodiments, workflow 300 can continue with an activity 312 ofthe payment item being received by first financial institution 202.Activity 312 can be similar or identical to activity 212 (FIG. 2).

In some embodiments, workflow 300 can continue with an activity 313 offirst financial institution 202 determining whether to make an inquiryto system 203 and/or storing the determination. Activity 313 can besimilar or identical to activity 213 (FIG. 2).

In many embodiments, workflow 300 can continue with an activity 314 offirst financial institution 202 sending an inquiry to system 203, and/orsystem 203 receiving the inquiry from first financial institution 202.Activity 314 can be similar or identical to activity 214 (FIG. 2).

In a number of embodiments, workflow 300 can continue with an activity315 of determining whether to route the inquiry to second financialinstitution 204 and/or storing the determination. In many embodiments,the routing decision can be based at least in part on a risk ofnon-payment of the payment item by the second entity. In manyembodiments, the routing decision can be based on information receivedfrom financial institutions (e.g., 131-134 (FIG. 1), which can includefirst financial institution 202 and/or second financial institution204), such as overnight batch data regarding whether accounts are openand in good status, what balances are available in the open accounts,whether accounts have had recent NSF or other activity, whether accountshad a stop payment order, and/or other suitable information. In someembodiments, system 203 can store the inquiry from first financialinstitution 202 received in activity 314 with or without a timestamp ofwhen the inquiry was received by system 203, and system 203 can usedatabase 111 (FIG. 1) to store the inquiry. In a number of embodiments,the routing decision can be based at least in part on other inquiriesreceived earlier in the same day that are similar to the inquiryreceived in activity 314. In some embodiments, the financialinstitutions (e.g., 131-134 (FIG. 1), first financial institution 202,and/or second financial institution 204) can provide additionalinformation to system 203 on a periodic or regular basis (e.g., daily,twice daily, hourly, half-hourly, on every transaction, etc.), which canbe received by system 203 before receiving the inquiry in activity 314,which can be more up-to-date than overnight batch data, and which can beused by system 203 in some embodiments to determine the routingdecision.

In several embodiments, the routing decision can be based on whethersecond financial institution 204 is setup to participate in onlineback-office validation to determine payment likelihood, and/or can bebased on rules that determine a risk of non-payment, based oninformation made available to system 203 from the financial institutions(e.g., 131-134 (FIG. 1), first financial institution 202, and/or secondfinancial institution 204) before receiving the inquiry in activity 314,based on earlier inquiries through system 203 (similar to the inquiryreceived in activity 314), and/or based on the inquiry received inactivity 314. In some embodiments, when system 203 applies the rules todetermines the risk of non-payment and the routing decision, system 203can generate decision information, which can be returned to firstfinancial institution 202 and/or sent to second financial institution204.

In various embodiments, system 203 can determine whether the paymentitem is drawn on an invalid account. If the account specified by thepayment item is not found, system 203 can generate decision informationindicating that the account was not found and can determine not to routethe inquiry to second financial institution 204.

In many embodiments, system 203 can determine whether the accountspecified by the payment item is open. If the account is closed, and hasbeen closed for more than a predetermined amount of time (e.g., 7 days),system 203 can generate decision information that the account is closedand determine not to route the inquiry to second financial institution204. In some embodiments, if the account has been closed for less than apredetermined amount of time (e.g., 7 days), system 203 can generatedecision information that the account has been recently closed and candetermine to route the inquiry to second financial institution 204.

In several embodiments, system 203 can determine, if the payment item isan ACH item, whether the account specified by the payment item has a“Post no Debits” status. If the account has a “Post no Debits” status,system 203 can generate decision information indicating that the accounthas a “Post no Debits” status and can determine not to route the inquiryto second financial institution 204.

In various embodiments, system 203 can determine, if the payment item isa check, whether the account specified by the payment item has a stoppayment on the item. For example, the stop payment can be based on athree-field match of routing number, account number, and serial number,or a four-field match of routing number account number, serial number,and payment amount. If the account has a stop payment status, system 203can generate decision information indicating that the account has a stoppayment status and can determine not to route the inquiry to secondfinancial institution 204.

In some embodiments, system 203 can determine, if the payment item is acheck, whether the account specified by the payment item uses PositivePay verification. In some embodiments, if the account uses Positive Payverification, system 203 can generate decision information indicatingthat the account has uses Positive Pay verification. In someembodiments, system 203 can determine not to route the inquiry to secondfinancial institution 204. In other embodiments, system 203 candetermine to route the inquiry to second financial institution 204 forPositive Pay verification.

In many embodiments, system 203 can determine, if the payment item is acheck, whether the check is likely a duplicate. If the check is likely aduplicate, system 203 can generate decision information indicating thatthe check is likely a duplicate and can determine not to route theinquiry to second financial institution 204.

In many embodiments, system 203 can determine, if the payment item is acheck, whether the check is likely a counterfeit. If the check is likelya counterfeit, system 203 can generate decision information indicatingthat the check is likely a counterfeit and can determine not to routethe inquiry to second financial institution 204.

In many embodiments, system 203 can determine whether the payment itemis likely part of a money-laundering scheme. For example, system 203 candetermine whether the payment item is likely part of a money-launderingscheme based on the payment amount of the payment item and/or othertransactions, and/or the payee and/or payor for the payment item. If thepayment item is likely part of a money-laundering scheme, system 203 cangenerate decision information indicating that the payment item is likelypart of a money-laundering scheme and can determine not to route theinquiry to second financial institution 204.

In many embodiments, system 203 can determine whether the payment itemis likely fraudulent. For example, system 203 can determine whether thepayment item is likely fraudulent based on the channel used, whether thechannel used is a new device, the authentication used in the channel,the location of the channel, whether the payor's account was recentlyopened, and/or whether the payment is consistent with transactionpatterns for the payor and/or payee. If the payment item is likelyfraudulent, system 203 can generate decision information indicating thatthe payment item is likely fraudulent and can determine not to route theinquiry to second financial institution 204.

In some embodiments, if system 203 has been provided with accountbalances (e.g., nightly, or more frequently), system 203 can determinewhether the payment amount specified by the payment item is greater thanthe latest balance information received by system 203. In someembodiments, system 203 can generate decision information indicatingthat the payment item is likely unable to be covered by the payor'saccount and can determine not to route the inquiry to second financialinstitution 204.

In various embodiments, system 203 can determine whether the paymentamount for the payment item is greater than or less than a predeterminedamount. For certain financial institutions, and/or for certain accountsat certain financial institutions, the financial institution (e.g.,either first financial institution 202 or second financial institution204) might not want to have the inquiry routed to second financialinstitution 204 if the payment amount if below a predetermined amount(e.g., a payment amount below $10, $50, or $100). In such cases, system203 can generate decision information indicating that the payment itemis below a certain amount and determine not to route the inquiry tosecond financial institution 204.

In a number of embodiments, system 203 can determine whether secondfinancial institution is setup to participate in online validation todetermine payment likelihood. If second financial institution is notsetup to participate in online validation, system 203 can generatedecision information indicating that second financial institution 204 isnot setup to participate in online validation, and can determine not toroute the inquiry to second financial institution 204.

In many embodiments, if system 203 has determined to not route theinquiry to second financial institution 204, system 203 can insteadrespond to first financial institution 202. In such cases, workflow 300can continue with an activity 316 of system 203 sending a response tofirst financial institution 202, and/or first financial institution 202receiving the response from system 203. In a number of embodiments, theresponse can be sent from system 203 to first financial institution 204in real-time after activity 314 of system 203 receiving the inquiry. Inmany embodiments, the response sent to first financial institution 202in activity 316 can include information from the inquiry and/or thedecision information generated by system 203 in activity 315.

If system 203 has determined to route the inquiry to second financialinstitution 204, workflow 300 can continue with an activity 317 ofsystem 203 sending an inquiry to second financial institution 204,and/or second financial institution 204 receiving the inquiry fromsystem 203. Activity 317 can be similar or identical to activity 216(FIG. 2). In some embodiments, the inquiry sent to second financialinstitution 204 in activity 317 can include the decision information,such as the determination of the risk of non-payment, generated bysystem 203 in activity 315, and/or the information received by system203 from first financial institution 202 in activity 314. In otherembodiments, the decision information generated by system 203 inactivity 315 can be sent to second financial institution 204 in aseparate informational message sent before or after the inquiry sent bysystem 203 to second financial institution 204 in activity 317. In yetother embodiments, after receiving the inquiry in activity 317, secondfinancial institution 204 can send a request for additional informationto system 203, and system 203 in response can send an informationalmessage to second financial institution 204 than includes the decisioninformation generated by system 203 in activity 315. In yet otherembodiments, second financial institution 204 can proceed to determinethe payment likelihood (described below) without the informationgenerated by system 203 in activity 315.

In several embodiments, workflow 300 can continue with an activity 318of second financial institution 204 determining a payment likelihoodand/or storing the determination. Activity 318 can be similar oridentical to activity 217 (FIG. 2). In various embodiments, determiningthe payment likelihood can be based at least in part on currentinformation of the payor's account maintained by second financialinstitution 204, information provided to second financial institution204 in the inquiry, and/or the decision information generated by system203 in activity 315. In many embodiments, the information available tosecond financial institution 204 can be different than the informationavailable to system 203. For example, the information available tosecond financial institution 204 can be current information, as opposedto information from the previous night, and/or one or more previousintra-day updates, which can beneficially allow second financialinstitution 204 to make decisions based on more current information. Insome embodiments, system 203 can have information about the payor and/orpayee at other financial institutions (e.g., 131-134 (FIG. 1)), whichcan beneficially allow system 203 to determine risks using aggregatedinformation that is not otherwise available to second financialinstitution 204. As such, the information provided by system 203 tosecond financial institution 204 in certain embodiments, such as thedecision information generated by system 203 in activity 315, canadvantageously enhance the ability of second financial institution 204to more accurately determine the payment likelihood, such as whether notto guarantee payment, whether or not to determine that payment islikely, and/or to accurately determine a payment likelihood score.

In many embodiments, workflow 300 can continue with an activity 319 ofsecond financial institution 204 sending a response to system 203,and/or system 203 receiving the response from second financialinstitution 204. Activity 319 can be similar or identical to activity218 (FIG. 2).

In various embodiments, workflow 300 can continue with an activity 320of system 203 storing the response sent from second financialinstitution 204 in activity 319. Activity 320 can be similar oridentical to activity 219 (FIG. 2).

In some embodiments, activity 320 can include system 203 furtherdetermining a payment likelihood based on the payment likelihooddetermined by and received from second financial institution 204 andalso based on additional information available to system 203. In theseembodiments, system 203 might have information that second financialinstitution 204 does not have, and therefore, system 203 can refine orfurther determine the payment likelihood that was originally made bysecond financial institution 204, and system 203 can store the refineddetermination. For example, as explained above with respect to activity315, system 203 may have additional financial information about thepayor's other bank accounts at other financial institutions that secondfinancial institution 204 does not have. Similarly, system 203 may havefinancial information about second financial institution 204 that is notpart of the response in activity 319 but that system 203 can use torefine or further determine the payment likelihood.

In some embodiments, workflow 300 can continue with an activity 321 ofsystem 203 system 203 sending a response to first financial institution202, and/or first financial institution 202 receiving the response fromsystem 203. Activity 321 can be similar or identical to activity 220(FIG. 2). In some embodiments, the decision information generated bysystem 203 in activity 315 can be added to the response to firstfinancial institution 202, and/or other risk factors, such as whetherthe account was recently opened.

In several embodiments, workflow 300 can continue after activity 316 oractivity 321 with an activity 322 of first financial institution 202determining whether to approve or deny the transaction, actuallyapproving or denying the transaction, storing the approval or denial,and/or notifying consumer 201 of such approval or denial. Activity 322can be similar or identical to activity 221 (FIG. 2). By incorporatinginsight from second financial institution 204 (e.g., the paymentlikelihood decision determined in activity 318) and/or system 203 (e.g.,the decision information generated in activity 315), first financialinstitution 202 can advantageously make a more informed decision indetermining the availability of funds for the payment item and indetermining whether to approve or deny the transaction.

In some embodiments, workflow 300 can optionally continue after activity322 with an activity 323 of first financial institution 202 sending apayment decision message to system 203, and/or system 203 receiving apayment decision message from first financial institution 202. In anumber of embodiments, the payment decision message can includeinformation regarding whether first financial institution 202 acceptedor denied the transaction. In some embodiments, the payment decisionmessage can be sent from first financial institution 202 in real-timeafter activity 316 or activity 321 of system 203 receiving the response.

In many embodiments, workflow 300 can continue with an activity 324 ofsystem 203 storing the payment decision message sent from firstfinancial institution 202 in activity 323. The payment decision messagecan be stored in database 111 (FIG. 1), and can include a timestamp ofwhen the payment decision message was received at system 203.

In some embodiments, workflow 300 can further optionally continue withan activity 325 of system 203 sending a payment decision message tosecond financial institution 204, and/or second financial institution204 receiving the payment decision message from system 203. In a numberof embodiments, the payment decision message can be sent from system 203to second financial institution 204 in real-time after activity 323 ofsystem 203 receiving the payment decision message in activity 323. Inmany embodiments, the payment decision message sent to second financialinstitution 204 in activity 325 can be similar or identical to thepayment decision message received by system 203 in activity 323.

In some embodiments, workflow 300 can further optionally continue withan activity 326 of second financial institution 204 storing the paymentdecision message sent from system 203 in activity 325. Second financialinstitution 204 also can store a timestamp of when the payment decisionmessage was received at second financial institution 204.

In various embodiments, the information in the payment decision messagesent to system 203 and/or second financial institution 204 from firstfinancial institution 202 can beneficially be used by system 203 and/orsecond financial institution 204 to determine risks in futuretransactions. In many embodiments, second financial institution 204 canuse the information in the payment decision message to update a pendingaccount status of the payor's account. In some embodiments, workflow 200(FIG. 2) can similarly include sending a payment decision message tosystem 203 and/or second financial institution 204 such that activities323, 324, 325, and 326 also can be part of workflow 200 (FIG. 2) byoccurring after activity 221 (FIG. 2).

Turning ahead in the drawings, FIG. 4 illustrates an exemplary workflow400 for real-time determination of funds availability sent from firstfinancial institution 202 to system 203 for determining a paymentlikelihood, according to various embodiments. Workflow 400 is merelyexemplary and is not limited to the embodiments presented herein.Workflow 400 can be employed in many different embodiments or examplesnot specifically depicted or described herein. In some embodiments, theprocedures, the processes, and/or the activities of workflow 400 can beperformed in the order presented. In other embodiments, the procedures,the processes, and/or the activities of workflow 400 can be performed inany suitable order. In still other embodiments, one or more of theprocedures, the processes, and/or the activities of workflow 400 can becombined or skipped. Workflow 400 can be similar to workflow 200 (FIG.2) and/or workflow 300 (FIG. 3), and various activities of workflow 400can be similar or identical to various activity of workflow 200 (FIG. 2)and/or workflow 300 (FIG. 3).

In some embodiments, workflow 400 can begin with an activity 411 of anentity, such as consumer 201, presenting a payment item for atransaction. Activity 411 can be similar or identical to activity 211(FIG. 2) and/or activity 311 (FIG. 3).

In many embodiments, workflow 400 can continue with an activity 412 ofthe payment item being received by first financial institution 202.Activity 412 can be similar or identical to activity 212 (FIG. 2) and/oractivity 312 (FIG. 3).

In some embodiments, workflow 400 can continue with an activity 413 ofdetermining whether to make an inquiry to system 203 and/or storing thedetermination. Activity 413 can be similar or identical to activity 213(FIG. 2) and/or activity 313 (FIG. 3).

In many embodiments, workflow 400 can continue with an activity 414 offirst financial institution 202 sending an inquiry to system 203, and/orsystem 203 receiving the inquiry from first financial institution 202.Activity 414 can be similar or identical to activity 214 (FIG. 2) and/oractivity 314 (FIG. 3).

In a number of embodiments, workflow 400 can continue with an activity415 of system 203 determining a payment likelihood. Activity 415 can besimilar to activity 217 (FIG. 2), activity 315 (FIG. 3), and/or activity318 (FIG. 3). In some embodiments, system 203 can store the inquiry fromfirst financial institution 202 received in activity 414 with or withouta timestamp of when the inquiry was received by system 203, and system203 can store the inquiry and/or timestamp in database 111 (FIG. 1). Ina number of embodiments, system 203 can apply one or more of the rulesapplied in making the routing decision in activity 315 (FIG. 3) todetermine a risk of non-payment, and/or system 203 can generate decisioninformation, such as the decision information generated in activity 315(FIG. 3), by applying the rules. System 203 can determine a paymentlikelihood based on the decision information and/or through applyingrules, such as the common consortium rules used to determine a paymentlikelihood in activity 217 (FIG. 2) and/or activity 318 (FIG. 3). Insome embodiments, a financial institution that is specified in a paymentitem as responsible for paying the payment item can provide informationregularly (e.g., twice daily, hourly, half-hourly, on each transaction,etc.) to system 203 so as to allow system 203 to determine the paymentlikelihood, rather than the financial institution determining thepayment likelihood (as done by second financial institution 204 inactivity 217 (FIG. 2) and activity 318 (FIG. 3)). In some embodiments,the financial institution can provide less, as much, or more informationto system 203 as is used by second financial institution 204 todetermine the payment likelihood in activity 217 (FIG. 2) and/oractivity 318 (FIG. 3).

In a number of embodiments, workflow 400 can continue with an activity416 of system 203 providing the payment likelihood information and/ordecision information generated in activity 415 to be stored in system203.

In several embodiments, workflow 400 can continue with an activity 417of system 203 storing the payment likelihood information and/or decisioninformation generated in activity 415 with or without a timestamp whenthe determination was made, in system 203, and system 203 can store theinformation and/or timestamp in database 111 (FIG. 1).

In many embodiments, workflow 400 can continue with an activity 418 ofsystem 203 sending a response to system first financial institution 202,and/or first financial institution 202 receiving the response fromsystem 203. Activity 417 can be similar to activity 218 (FIG. 2),activity 220 (FIG. 2), activity 319 (FIG. 3), and/or activity 321 (FIG.3). The response can include the decision information and/or the paymentresponse likelihood information, as determined in activity 415, and/orother risk factors, such as whether the account was recently opened.

In several embodiments, workflow 400 can continue with an activity 419of first financial institution 202 determining whether to approve ordeny the transaction, actually approving or denying the transaction,storing the approval or denial, and/or notifying consumer 201 of suchapproval or denial. Activity 422 can be similar or identical to activity221 (FIG. 2) and/or activity 322 (FIG. 3). In some embodiments, workflow400 can optionally send the payment decision information to system 203,as described in activities 323 and 324 in FIG. 3.

Turning ahead in the drawings, FIG. 5 illustrates a flow chart for amethod 500 to facilitate determining an availability of funds for apayment item, according to an embodiment. Method 500 is merely exemplaryand is not limited to the embodiments presented herein. Method 500 canbe employed in many different embodiments or examples not specificallydepicted or described herein. In some embodiments, the procedures, theprocesses, and/or the activities of method 500 can be performed in theorder presented. In other embodiments, the procedures, the processes,and/or the activities of method 500 can be performed in any suitableorder. In still other embodiments, one or more of the procedures, theprocesses, and/or the activities of method 500 can be combined orskipped. Method 500 can be similar or identical to the acts performed bysystem 203 (FIGS. 2-4) in workflow 200 (FIG. 2). In many embodiments,the payment item can include one of a check or an ACH item.

Referring to FIG. 5, method 500 can include a block 501 of providing aprocessing mechanism in data communication through a network with afirst entity and a plurality of depository financial institutions. Thefirst entity can be similar or identical to first financial institution202 (FIGS. 2-4). The processing mechanism can be similar or identical tosystem 110 (FIG. 1) and/or system 203 (FIGS. 2-4). The network can besimilar or identical to network 120 (FIG. 1). The depository financialinstitutions can be similar or identical to financial institutions131-134 (FIG. 1), first financial institution 202 (FIGS. 2-4), and/orsecond financial institution 204 (FIGS. 2-3). In some embodiments, theplurality of depository financial institutions can include a secondentity. The second entity can be similar or identical to secondfinancial institution 204 (FIGS. 2-3). In some embodiments, the secondentity can be specified by the payment item as being responsible forpaying the payment item. In many embodiments, the first entity can bedifferent from the second entity. In some embodiments, the payment itemcan be a check, the first entity can be a depository financialinstitution receiving the check for deposit, and the second entity canbe a depository financial institution against which the check has beendrawn. In other embodiments, the payment item can be an ACH item, thefirst entity can be an originating depository financial institution(ODFI) for the ACH item, and the second entity can be a receivingdepository financial institution (RDFI) for the ACH item. In a number ofembodiments, the first entity can be a payment processor, and the secondentity can be a financial institution.

In many embodiments, method 500 additionally can include a block 502 ofreceiving a first inquiry at the processing mechanism through thenetwork from the first entity. The first inquiry can be similar oridentical to the inquiry sent from first financial institution 202(FIGS. 2-4) to system 203 (FIGS. 2-4) in activity 214 (FIG. 2). Invarious embodiments, the first inquiry can be received from the firstentity in real-time after the first entity receives the payment item.For example, the first entity can receive the payment item similarly oridentically to first financial institution 202 (FIGS. 2-4) receiving thepayment item in activity 212 (FIG. 2).

In some embodiments, method 500 further can include a block 503 ofstoring the first inquiry received from the first entity along with afirst timestamp that indicates when the first inquiry was received fromthe first entity. Block 503 of storing the first inquiry can be similaror identical to activity 215 (FIG. 2) of system 203 (FIGS. 2-4) storingthe inquiry sent from first financial institution 202 (FIGS. 2-4).

In many embodiments, method 500 additionally can include a block 504 ofsending a second inquiry from the processing mechanism through thenetwork to the second entity in real-time after receiving the firstinquiry. The second inquiry can be similar or identical to the inquirysent from system 203 (FIGS. 2-4) to second financial institution 204(FIGS. 2-3) in activity 216 (FIG. 2), and block 504 can be similar oridentical to activity 216 (FIG. 2). In various embodiments, the secondinquiry can be based at least in part on the first inquiry. In someembodiments, the first and/or second inquiries can include a routingnumber of the second entity that is specified by the payment item; anaccount number of the account maintained by the second entity that isspecified by the payment item; a payment amount that is specified by thepayment item; an identifier of the first entity; a transaction channelidentifier that indicates the channel through which a transacting entitypresented the payment item to the first entity; a payment distributionmethod identifier that indicates how the transacting entity requested tobe paid for the payment item by the first entity; an account number ofthe first entity associated with the transacting entity; and/or, if thepayment item is a check, a serial number of the check. In a number ofembodiments, the first inquiry can include an identifier linked to theaccount maintained by the second entity that is specified by the paymentitem.

In some embodiments, method 500 further can include a block 505 ofreceiving a first response at the processing mechanism through thenetwork from the second entity. The first response can be similar oridentical to the response sent from second financial institution 204(FIGS. 2-3) to system 203 (FIGS. 2-4) in activity 218 (FIG. 2), andblock 505 can be similar or identical to activity 281 (FIG. 2). Invarious embodiments, the first response can be sent by the second entityin real-time in response to receiving the second inquiry.

In many embodiments, method 500 additionally can include a block 506 ofstoring the first response received from the second entity along with asecond timestamp that indicates when the first response was receivedfrom the second entity. Block 506 of storing the first response can besimilar or identical to activity 219 (FIG. 2) of system 203 (FIGS. 2-4)storing the response sent from second financial institution 204 (FIGS.2-3).

In some embodiments, method 500 further can include a block 507 ofsending a second response from the processing mechanism through thenetwork to the first entity in real-time after receiving the firstresponse. The second response can be similar or identical to theresponse sent from system 203 (FIGS. 2-4) to first financial institution202 (FIGS. 2-4) in activity 220 (FIG. 2), and block 507 can be similarto activity 220 (FIG. 2). In various embodiments, the second responsecan be sent within 30 seconds of receiving the first inquiry. In someembodiments, the second response can be based at least in part on thefirst response. In some embodiments, the first and/or second responseseach can include a payment likelihood indicator provided by the secondentity that indicates a likelihood of the second entity to pay thepayment item. The payment likelihood indicator can be similar oridentical to the payment likelihood indicator determined by secondfinancial institution 204 (FIGS. 2-3) in activity 217 (FIG. 2). Invarious embodiments, the payment likelihood indicator can be based atleast in part on a current status and a current available balance of anaccount maintained by the second entity that is specified by the paymentitem for payment of the payment item. In a number of embodiments, thepayment likelihood indicator in the first and/or second responses caninclude an indication of whether or not the second entity guaranteespayment of the payment item. In many embodiments, the payment likelihoodindicator in the first and/or second responses can include a score. Thescore can be similar or identical to the payment likelihood scoredetermined by second financial institution 204 (FIGS. 2-3) in activity217 (FIG. 2). In various embodiments, the first and/or second responseseach can further include one or more reason indicators to explain thepayment likelihood indicator provided by the second entity. The reasonindicators can be similar or identical to the reason indicatorsdetermined by second financial institution 204 (FIGS. 2-3) in activity217 (FIG. 2).

Turning ahead in the drawings, FIG. 6 illustrates a flow chart for amethod 600 to facilitate determining an availability of funds for apayment item, according to an embodiment. Method 600 is merely exemplaryand is not limited to the embodiments presented herein. Method 600 canbe employed in many different embodiments or examples not specificallydepicted or described herein. In some embodiments, the procedures, theprocesses, and/or the activities of method 600 can be performed in theorder presented. In other embodiments, the procedures, the processes,and/or the activities of method 600 can be performed in any suitableorder. In still other embodiments, one or more of the procedures, theprocesses, and/or the activities of method 600 can be combined orskipped. Method 600 can be similar or identical to the acts performed bysystem 203 (FIGS. 2-4) in workflow 300 (FIG. 3). In many embodiments,the payment item can include one of a check or an ACH item.

Referring to FIG. 6, method 600 can include a block 601 of receiving afirst inquiry through a network from a first entity. The first entitycan be similar or identical to first financial institution 202 (FIGS.2-4). The network can be similar or identical to network 120 (FIG. 1).The first inquiry can be similar or identical to the inquiry sent fromfirst financial institution 202 (FIGS. 2-4) to system 203 (FIGS. 2-4) inactivity 314 (FIG. 3), and block 610 can be similar or identical toactivity 315 (FIG. 3). In a number of embodiments, the first inquiry canbe received from the first entity in real-time after the first entityreceives the payment item. For example, the first entity can receive thepayment item similarly or identical to first financial institution 202(FIGS. 2-4) receiving the payment item in activity 312 (FIG. 3).

In many embodiments, method 600 additionally can include a block 602 ofdetermining a routing decision of whether or not to route the firstinquiry to a second entity. Block 602 of determining the routingdecision can be similar or identical to activity 315 (FIG. 3) of system203 (FIGS. 2-4) determining whether to route the inquiry to secondfinancial institution 204 (FIGS. 2-3). The second entity can be similaror identical to second financial institution 204 (FIGS. 2-3). In manyembodiments, the first entity can be different from the second entity.In various embodiments, the second entity can be a depository financialinstitution that is specified by the payment item as responsible forpaying the payment item. In a number of embodiments, the routingdecision can be based at least in part on a risk of non-payment of thepayment item by the second entity. In some embodiments, the payment itemcan be a check, the first entity can be a depository financialinstitution receiving the check for deposit, and the second entity canbe a depository financial institution against which the check has beendrawn. In other embodiments, the payment item can be an ACH item, thefirst entity can be an originating depository financial institution(ODFI) for the ACH item, and the second entity can be a receivingdepository financial institution (RDFI) for the ACH item.

In several embodiments, determining the routing decision can includedetermining the routing decision based at least on part on account datareceived from a plurality of financial institutions for accountsmaintained by the financial institutions. The financial institutions canbe similar or identical to financial institutions 131-134 (FIG. 1),first financial institution 202 (FIGS. 2-4), and/or second financialinstitution 204 (FIGS. 2-3). In various embodiments, the account datacan be received before receiving the first inquiry. In many embodiments,the plurality of financial institutions can include the second entity.In some embodiments, the payment item can specify for payment a firstaccount of the accounts. In a number of embodiments, the first accountcan be maintained by the second entity. In some embodiments, the accountdata can include first account data for the first account.

In various embodiments, determining the routing decision further caninclude determining the routing decision such that the routing decisionis to not route the first inquiry to the second entity when it isdetermined, based on the first account data, that the first account isnot valid. In many embodiments, determining the routing decision furthercan include determining the routing decision such that the routingdecision is to not route the first inquiry to the second entity when itis determined, based on the first account data, that the first accounthas been closed for a predetermined amount of time. In a number ofembodiments, determining the routing decision further can includedetermining the routing decision such that the routing decision is tonot route the first inquiry to the second entity when the payment itemcomprises an ACH item and it is determined, based on the first accountdata, that the first account has a post no debits status. In someembodiments, determining the routing decision further can includedetermining the routing decision such that the routing decision is tonot route the first inquiry to the second entity when the payment itemcomprises a check and it is determined, based on the first account data,that the first account has a stop payment on the check. In severalembodiments, determining the routing decision further can includedetermining the routing decision such that the routing decision is tonot route the first inquiry to the second entity when the payment itemcomprises a check and it is determined, based on the first account data,the first account uses positive pay verification. In variousembodiments, determining the routing decision further can includedetermining the routing decision such that the routing decision is tonot route the first inquiry to the second entity when it is determined,based on the first account data, the payment item is likely a duplicate.In many embodiments, determining the routing decision further caninclude determining the routing decision such that the routing decisionis to not route the first inquiry to the second entity when, based onthe first account data, a payment amount of payment item is determinedto be below a predetermined threshold amount.

In some embodiments, method 600 further can include, if the routingdecision is to not route the first inquiry to the second entity, a block603 of sending a first response through the network to the first entityin real-time after receiving the first inquiry. Block 603 can be similaror identical to activity 316 (FIG. 3), and the first response can besimilar or identical to the response sent from system 203 (FIGS. 2-4) tofirst financial institution 202 (FIGS. 2-4) in activity 316 (FIG. 3). Insome embodiments, sending the first response to the first entity caninclude sending the first response such that the first response includesinformation derived in determining the routing decision. For example,the information can be similar or identical to the decision informationgenerated by system 203 (FIGS. 2-4) in activity 315 (FIG. 3).

In certain embodiments, method 600 can optionally include, if therouting decision is to route the first inquiry to the second entity, ablock 604 of sending an informational message through the network to thesecond entity in real-time after receiving the first inquiry. In someembodiments, the informational message can include information derivedfrom determining the routing decision. For example, the information canbe similar or identical to the decision information generated by system203 (FIGS. 2-4) in activity 315 (FIG. 3), and block 604 can be similaror identical to activity 317 (FIG. 3).

In many embodiments, method 600 additionally can include, if the routingdecision is to route the first inquiry to the second entity, after block602 or block 604, a block 605 of sending a second inquiry through thenetwork to the second entity in real-time after receiving the firstinquiry. The second inquiry can be similar or identical to the inquirysent from system 203 (FIGS. 2-4) to second financial institution 204(FIGS. 2-3) in activity 317 (FIG. 3), and block 605 can be similar toactivity 317 (FIG. 3). In various embodiments, the second inquiry can bebased at least in part on the first inquiry. In some embodiments, thefirst and/or second inquiries can include a routing number of the secondentity that is specified by the payment item; an account number of thesecond entity that is specified by the payment item; a payment amountthat is specified by the payment item; an identifier of the firstentity; a transaction channel identifier that indicates the channelthrough which a transacting entity presented the payment item to thefirst entity; a payment distribution method identifier that indicateshow the transacting entity requested to be paid for the payment item bythe first entity; an account number of the first entity associated withthe transacting entity; and/or, if the payment item is a check, a serialnumber of the check. In some embodiments, sending the second inquiry tothe second entity can include sending the second inquiry such that thesecond inquiry further includes information derived from determining therouting decision. For example, the information can be similar oridentical to the decision information generated by system 203 (FIGS.2-4) in activity 315 (FIG. 3).

In certain embodiments, method 600 can optionally include, such as insome embodiments when block 604 was skipped, a block 606 of receiving arequest for additional information through the network from the secondentity.

In certain embodiments, method 600 can further optionally include, afterblock 606, a block 607 of sending an informational message through thenetwork to the second entity in real-time after receiving the requestfor additional information. The informational message can includeinformation derived from determining the routing decision. For example,the information can be similar or identical to the decision informationgenerated by system 203 (FIGS. 2-4) in activity 315 (FIG. 3). Blocks 606and 607 can be similar to activity 317 (FIG. 3).

In many embodiments, method 600 additionally can include, after block605 or block 607, a block 608 of receiving a second response through thenetwork from the second entity. The first response can be similar oridentical to the response sent from second financial institution 204(FIGS. 2-3) to system 203 (FIGS. 2-4) in activity 319 (FIG. 3), andblock 608 can be similar or identical to activity 319 (FIG. 3). Invarious embodiments, the first response can be sent by the second entityin real-time in response to receiving the second inquiry.

In some embodiments, method 600 further can include a block 609 ofstoring the second response received from the second entity along with atimestamp that indicates when the second response was received from thesecond entity. Block 609 of storing the second response can be similaror identical to activity 320 (FIG. 3) of system 203 (FIGS. 2-4) storingthe response sent from second financial institution 204 (FIGS. 2-3).

In many embodiments, method 600 additionally can include a block 610 ofsending a third response through the network to the first entity inreal-time after receiving the second response. The third response can besimilar or identical to the response sent from system 203 (FIGS. 2-4) tofirst financial institution 202 (FIGS. 2-4) in activity 321 (FIG. 3),and block 610 can be similar or identical to activity 321 (FIG. 3). Invarious embodiments, the third response can be based at least in part onthe second response. In some embodiments, the second and/or thirdresponses can include a payment likelihood indicator provided by thesecond entity that indicates a likelihood of the second entity to paythe payment item. The payment likelihood indicator can be similar oridentical to the payment likelihood indicator determined by secondfinancial institution 204 (FIGS. 2-3) in activity 318 (FIG. 3). Invarious embodiments, the payment likelihood indicator can be based atleast in part on a current status and a current available balance of anaccount maintained by the second entity that is specified by the paymentitem for payment of the payment item. In some embodiments, the one ormore processing modules (e.g., system 203 (FIGS. 2-4) can be in datacommunication through the network with a plurality of financialinstitutions that have each agreed to apply common standards fordetermining the payment likelihood indicator. The financial institutionscan be similar or identical to financial institutions 131-134 (FIG. 1),first financial institution 202 (FIGS. 2-4), and/or second financialinstitution 204 (FIGS. 2-3). The common standards can be similar oridentical to the common consortium rules described above in connectionwith activity 318 (FIG. 3). In several embodiments, the second entitycan be any one of the plurality of financial institutions, as specifiedby the payment item. In some embodiments, sending the third response tothe first entity can include sending the third response such that thethird response further includes information derived from determining therouting decision. For example, the information can be similar oridentical to the decision information generated by system 203 (FIGS.2-4) in activity 315 (FIG. 3).

In a number of embodiments, the payment likelihood indicator in thesecond and/or third responses can include an indication of whether ornot the second entity guarantees payment of the payment item. In manyembodiments, the payment likelihood indicator in the second and/or thirdresponses can include a score. The score can be similar or identical tothe payment likelihood score determined by second financial institution204 (FIGS. 2-3) in activity 217 (FIG. 2). In various embodiments, thesecond and/or third responses each can further include one or morereason indicators to explain the payment likelihood indicator providedby the second entity. The reason indicators can be similar or identicalto the reason indicators determined by second financial institution 204(FIGS. 2-3) in activity 217 (FIG. 2). In various embodiments, one of thefirst response or the third response can be sent within 30 seconds ofreceiving the first inquiry.

In certain embodiments, method 600 optionally can include, after block603 or block 610, a block 611 of sending an informational messagethrough the network to the second entity including information derivedfrom determining the routing decision. For example, the information canbe similar or identical to the decision information generated by system203 (FIGS. 2-4) in activity 315 (FIG. 3).

In certain embodiments, method 600 optionally can include, after block603 or block 610, a block 612 of receiving a first payment decisionmessage through the network from the first entity that indicates whetherthe first entity paid the payment item. For example, the first paymentdecision message can be similar to the payment decision message receivedby system 203 (FIGS. 2-4) in activity 323 (FIG. 3), and block 612 can besimilar or identical to activity 323 (FIG. 3).

In certain embodiments, method 600 can include, after block 612, a block613 of sending a second payment decision message through the network tothe second entity, the second payment decision message being based atleast in part on the first payment decision message. For example, thesecond payment decision message can be similar to the payment decisionmessage sent by system 203 (FIGS. 2-4) in activity 325 (FIG. 3), andblock 613 can be similar or identical to activity 325 (FIG. 3). In manyembodiments, sending the second payment decision message to the secondentity can include sending the second payment message such that thesecond payment message further includes information derived fromdetermining the routing decision. For example, the information can besimilar or identical to the decision information generated by system 203(FIGS. 2-4) in activity 315 (FIG. 3).

Turning ahead in the drawings, FIG. 7 illustrates a flow chart for amethod 700 to facilitate determining an availability of funds for apayment item, according to an embodiment. Method 700 is merely exemplaryand is not limited to the embodiments presented herein. Method 700 canbe employed in many different embodiments or examples not specificallydepicted or described herein. In some embodiments, the procedures, theprocesses, and/or the activities of method 700 can be performed in theorder presented. In other embodiments, the procedures, the processes,and/or the activities of method 700 can be performed in any suitableorder. In still other embodiments, one or more of the procedures, theprocesses, and/or the activities of method 700 can be combined orskipped. Method 700 can be similar or identical to the acts performed bysystem 203 (FIGS. 2-4) in workflow 400 (FIG. 5). In many embodiments,the payment item can include one of a check or an ACH item.

Referring to FIG. 7, method 700 can include a block 701 of receiving atleast hourly updated account data comprising current statuses andcurrent available balances of accounts maintained by one or moredepository financial institutions. The financial institutions can besimilar or identical to financial institutions 131-134 (FIG. 1), firstfinancial institution 202 (FIGS. 2-4), and/or second financialinstitution 204 (FIGS. 2-3).

In many embodiments, method 700 additionally can include a block 702 ofreceiving an inquiry through a network from a first entity. The firstentity can be similar or identical to first financial institution 202(FIGS. 2-4). The network can be similar or identical to network 120(FIG. 1). The inquiry can be similar or identical to the inquiry sentfrom first financial institution 202 (FIGS. 2-4) to system 203 (FIGS.2-4) in activity 414 (FIG. 4), and block 702 can be similar or identicalto activity 414 (FIG. 4). In a number of embodiments, the inquiry can bereceived from the first entity in real-time after the first entityreceives the payment item. For example, the first entity can receive thepayment item similarly or identical to first financial institution 202(FIGS. 2-4) receiving the payment item in activity 412 (FIG. 23). Invarious embodiments, the payment item can specify a second entity asresponsible for paying the payment item. The second entity can besimilar or identical to second financial institution 204 (FIGS. 2-3). Inmany embodiments, the first entity can be different from the secondentity. In some embodiments, the payment item can specify an accountmaintained by the second entity for payment of the payment item. In anumber of embodiments, one of the one or more depository financialinstitutions can include the second entity.

In a number of embodiments, the payment item can be a check, the firstentity can be a depository financial institution receiving the check fordeposit, and the second entity can be a depository financial institutionagainst which the check has been drawn. In other embodiments, thepayment item can be an ACH item, the first entity can be an originatingdepository financial institution (ODFI) for the ACH item, and the secondentity can be a receiving depository financial institution (RDFI) forthe ACH item. In several embodiments, the inquiry can include a routingnumber of the second entity that is specified by the payment item; anaccount number maintained by the second entity that is specified by thepayment item; a payment amount that is specified by the payment item; anidentifier of the first entity; a transaction channel identifier thatindicates the channel through which a transacting entity presented thepayment item to the first entity; a payment distribution methodidentifier that indicates how the transacting entity requested to bepaid for the payment item by the first entity; an account number of thefirst entity associated with the transacting entity; and/or, if thepayment item is a check, a serial number of the check.

In some embodiments, method 700 further can include a block 703 ofdetermining a payment likelihood indicator based at least in part on astatus and an available balance of the account as updated by the updatedaccount data. The payment likelihood indicator can be similar oridentical to the payment likelihood indicator determined by secondfinancial institution 204 (FIGS. 2-3) in activity 415 (FIG. 4), andblock 703 can be similar to activity 415 (FIG. 4).

In many embodiments, method 700 additionally can include a block 704 ofstoring the payment likelihood indicator. For example, block 704 ofstoring the payment likelihood indicator can be similar or identical toactivity 417 (FIG. 4) of system 203 (FIGS. 2-4) storing the paymentlikelihood indicator.

In some embodiments, method 700 further can include a block 705 ofsending a response through the network to the first entity in real-timeafter receiving the inquiry. The response can be similar or identical tothe response sent from system 203 (FIGS. 2-4) to first financialinstitution 202 (FIGS. 2-4) in activity 418 (FIG. 4), and block 705 canbe similar or identical to activity 418 (FIG. 4). In a number ofembodiments, the response can include the payment likelihood indicator.

In various embodiments, the payment likelihood indicator can indicate alikelihood of the second entity to pay the payment item. In a number ofembodiments, the payment likelihood indicator in the response caninclude an indication of whether or not the second entity guaranteespayment of the payment item. In many embodiments, the payment likelihoodindicator in the response can include a score. The score can be similaror identical to the payment likelihood score determined by system 203(FIGS. 2-4) in activity 415 (FIG. 4). In various embodiments, theresponse can further include one or more reason indicators to explainthe payment likelihood indicator. The reason indicators can be similaror identical to the reason indicators determined by system 203 (FIGS.2-3) in activity 415 (FIG. 4). In various embodiments, the response canbe sent within 30 seconds of receiving the inquiry.

Returning to FIG. 1, as described above, system 110 can include one ormore modules, such as communications module 112, data module 113, riskengine 114, and/or likelihood calculation engine 115. System 110 and themodules therein are merely exemplary and are not limited to theembodiments presented herein. System 110 can be employed in manydifferent embodiments or examples not specifically depicted or describedherein. In some embodiments, certain elements or modules of system 110can perform various procedures, processes, and/or acts. In otherembodiments, the procedures, processes, and/or acts can be performed byother suitable elements or modules.

In many embodiments, communications module 112 can at least partiallyperform block 502 (FIG. 5) of receiving a first inquiry at theprocessing mechanism through the network from the first entity, block504 (FIG. 5) of sending a second inquiry from the processing mechanismthrough the network to the second entity in real-time after receivingthe first inquiry, block 505 (FIG. 5) of receiving a first response atthe processing mechanism through the network from the second entity,block 507 (FIG. 5) of sending a second response from the processingmechanism through the network to the first entity in real-time afterreceiving the first response, block 601 (FIG. 6) of receiving a firstinquiry through a network from a first entity, block 603 (FIG. 6) ofsending a first response through the network to the first entity inreal-time after receiving the first inquiry, block 604 (FIG. 6) ofsending an informational message through the network to the secondentity in real-time after receiving the first inquiry, block 605 (FIG.6) of sending a second inquiry through the network to the second entityin real-time after receiving the first inquiry, block 606 (FIG. 6) ofreceiving a request for additional information through the network fromthe second entity, block 607 (FIG. 6) of sending an informationalmessage through the network to the second entity in real-time afterreceiving the request for additional information, block 608 (FIG. 6) ofreceiving a second response through the network from the second entity,block 610 (FIG. 6) of sending a third response through the network tothe first entity in real-time after receiving the second response, block611 (FIG. 6) of sending an informational message through the network tothe second entity including information derived from determining therouting decision, block 612 (FIG. 6) of receiving a first paymentdecision message through the network from the first entity thatindicates whether the first entity paid the payment item, block 613(FIG. 6) of sending a second payment decision message through thenetwork to the second entity, block 701 (FIG. 7) of receiving at leasthourly updated account data comprising current statuses and currentavailable balances of accounts maintained by one or more depositoryfinancial institutions, block 702 (FIG. 7) of receiving an inquirythrough a network from a first entity, and/or block 705 (FIG. 7) ofsending a response through the network to the first entity in real-timeafter receiving the inquiry.

In several embodiments, data module 113 can at least partially performblock 503 (FIG. 5) of storing the first inquiry received from the firstentity along with a first timestamp that indicates when the firstinquiry was received from the first entity, block 506 (FIG. 5) ofstoring the first response received from the second entity along with asecond timestamp that indicates when the first response was receivedfrom the second entity, block 609 (FIG. 6) of storing the secondresponse received from the second entity along with a timestamp thatindicates when the second response was received from the second entity,and/or block 704 (FIG. 7) of storing the payment likelihood indicator.In some embodiments, module 113 also can perform portions of block 602(FIG. 6) and block 703 (FIG. 7).

In many embodiments, risk engine 114 can at least partially performblock 602 (FIG. 6) of determining a routing decision of whether or notto route the first inquiry to a second entity. Furthermore, as explainedabove for activity 320 (FIG. 3), some embodiments of risk engine 114also can at least partially perform block 609 (FIG. 6) when block 320(FIG. 3) refines or further determines the payment likelihood afterreceiving the originally determined payment likelihood from the secondfinancial institution.

In several embodiments, likelihood calculation engine 115 can at leastpartially perform block 703 (FIG. 7) of determining a payment likelihoodindicator based at least in part on a status and an available balance ofthe account as updated by the updated account data

In various embodiments, the techniques described herein can beneficiallyconnect in real-time a depository bank, an originator, or a paymentacceptor with information from the paying bank about a payment item inorder to deliver more intelligence as to the likelihood that the paymentitem will pay. These techniques can advantageously provide the payingbank with insight as to check and/or ACH items that will clear in thenear term. In many embodiments, the techniques described herein canallow financial institutions to connect to a single entity (e.g., server110 (FIG. 1) or server 203 (FIGS. 2-4) to connect to multiple financialinstitutions for query and responses, and/or to access fraud-preventionservices.

Turning ahead in the drawings, FIG. 8 illustrates a computer 800, all ofwhich or a portion of which can be suitable for implementing anembodiment of at least a portion of system 110 (FIG. 1), system 203(FIGS. 2-4), system 1000 (FIGS. 10-11), system 1200 (FIG. 12); system1300 (FIGS. 13-14), system 1500 (FIGS. 15-16), system 1700 (FIG. 17),transaction system 1050 (FIGS. 10-17, 28), sending participant (FIGS.10-17, 28), receiving participant (FIGS. 10-17, 28), application serviceprovider 1030 (FIGS. 10-12), application service provider 1330 (FIGS.13-14), application service provider 1530 (FIGS. 15-17), and/orapplication service provider 2830 (FIG. 28), and/or the techniquesdescribed in workflow 200 (FIG. 2), workflow 300 (FIG. 3), workflow 400(FIG. 4), method 500 (FIG. 5), method 600 (FIG. 6), method 700 (FIG. 7),method 1800 (FIG. 18), block 1801 (FIG. 19), block 1802 (FIG. 20),method 2100 (FIG. 21), method 2200 (FIG. 22), block 2201 (FIG. 23),method 2400 (FIG. 24), block 2401 (FIG. 25), method 2600 (FIG. 26),and/or block 2601 (FIG. 27). Computer 800 includes a chassis 802containing one or more circuit boards (not shown), a USB (universalserial bus) port 812, a Compact Disc Read-Only Memory (CD-ROM) and/orDigital Video Disc (DVD) drive 816, and a hard drive 814. Arepresentative block diagram of the elements included on the circuitboards inside chassis 802 is shown in FIG. 9. A central processing unit(CPU) 910 in FIG. 9 is coupled to a system bus 914 in FIG. 9. In variousembodiments, the architecture of CPU 910 can be compliant with any of avariety of commercially distributed architecture families.

Continuing with FIG. 9, system bus 914 also is coupled to memory 908that includes both read only memory (ROM) and random access memory(RAM). Non-volatile portions of memory storage unit 908 or the ROM canbe encoded with a boot code sequence suitable for restoring computer 800(FIG. 8) to a functional state after a system reset. In addition, memory908 can include microcode such as a Basic Input-Output System (BIOS). Insome examples, the one or more memory storage units of the variousembodiments disclosed herein can comprise memory storage unit 908, aUSB-equipped electronic device, such as, an external memory storage unit(not shown) coupled to universal serial bus (USB) port 812 (FIGS. 8-9),hard drive 814 (FIGS. 8-9), and/or CD-ROM or DVD drive 816 (FIGS. 8-9).In the same or different examples, the one or more memory storage unitsof the various embodiments disclosed herein can comprise an operatingsystem, which can be a software program that manages the hardware andsoftware resources of a computer and/or a computer network. Theoperating system can perform basic tasks such as, for example,controlling and allocating memory, prioritizing the processing ofinstructions, controlling input and output devices, facilitatingnetworking, and managing files. Some examples of common operatingsystems can comprise Microsoft® Windows® operating system (OS), Mac® OS,UNIX® OS, and Linux® OS.

As used herein, “processor” and/or “processing module” means any type ofcomputational circuit, such as but not limited to a microprocessor, amicrocontroller, a controller, a complex instruction set computing(CISC) microprocessor, a reduced instruction set computing (RISC)microprocessor, a very long instruction word (VLIW) microprocessor, agraphics processor, a digital signal processor, or any other type ofprocessor or processing circuit capable of performing the desiredfunctions. In some examples, the one or more processors of the variousembodiments disclosed herein can comprise CPU 910.

In the depicted embodiment of FIG. 9, various I/O devices such as a diskcontroller 904, a graphics adapter 924, a video controller 902, akeyboard adapter 926, a mouse adapter 906, a network adapter 920, andother I/O devices 922 can be coupled to system bus 914. Keyboard adapter926 and mouse adapter 906 are coupled to a keyboard 804 (FIGS. 8 and 9)and a mouse 810 (FIGS. 8 and 9), respectively, of computer 800 (FIG. 8).While graphics adapter 924 and video controller 902 are indicated asdistinct units in FIG. 9, video controller 902 can be integrated intographics adapter 924, or vice versa in other embodiments. Videocontroller 902 is suitable for refreshing a monitor 806 (FIGS. 8 and 9)to display images on a screen 808 (FIG. 8) of computer 800 (FIG. 8).Disk controller 904 can control hard drive 814 (FIGS. 8 and 9), USB port812 (FIGS. 8 and 9), and CD-ROM or DVD drive 816 (FIGS. 8 and 9). Inother embodiments, distinct units can be used to control each of thesedevices separately.

In some embodiments, network adapter 920 can comprise and/or beimplemented as a WNIC (wireless network interface controller) card (notshown) plugged or coupled to an expansion port (not shown) in computersystem 800 (FIG. 8). In other embodiments, the WNIC card can be awireless network card built into computer system 800 (FIG. 8). Awireless network adapter can be built into computer system 800 (FIG. 8)by having wireless communication capabilities integrated into themotherboard chipset (not shown), or implemented via one or morededicated wireless communication chips (not shown), connected through aPCI (peripheral component interconnector) or a PCI express bus ofcomputer system 800 (FIG. 8) or USB port 812 (FIG. 8). In otherembodiments, network adapter 920 can comprise and/or be implemented as awired network interface controller card (not shown).

Although many other components of computer 800 (FIG. 8) are not shown,such components and their interconnection are well known to those ofordinary skill in the art. Accordingly, further details concerning theconstruction and composition of computer 800 and the circuit boardsinside chassis 802 (FIG. 8) need not be discussed herein.

When computer 800 in FIG. 8 is running, program instructions stored on aUSB drive in USB port 812, on a CD-ROM or DVD in CD-ROM and/or DVD drive816, on hard drive 814, or in memory 908 (FIG. 9) are executed by CPU910 (FIG. 9). A portion of the program instructions, stored on thesedevices, can be suitable for carrying out all or at least part of thetechniques described herein.

Although computer system 800 is illustrated as a desktop computer inFIG. 8, there can be examples where computer system 800 may take adifferent form factor while still having functional elements similar tothose described for computer system 800. In some embodiments, computersystem 800 may comprise a single computer, a single server, or a clusteror collection of computers or servers, or a cloud of computers orservers. Typically, a cluster or collection of servers can be used whenthe demand on computer system 800 exceeds the reasonable capability of asingle server or computer. In certain embodiments, computer system 800may comprise a portable computer, such as a laptop computer. In certainother embodiments, computer system 800 may comprise a mobile device,such as a smartphone. In certain additional embodiments, computer system800 may comprise an embedded system.

In many embodiments, after a biller sends a bill to a customer, thecustomer can send a payment to the biller such that the biller can havereal-time availability of funds. Various embodiments of a system forpayment with real-time funds availability can include a payor (alsoreferred to as a sender or the customer), an application serviceprovider, a sending participant, and application sponsor, a transactionsystem, a receiving participant, the biller (also referred to as arecipient), and/or other suitable elements, as shown in one or more ofFIGS. 10-17 and described below. In many embodiments, the transactionsystem can provide for real-time communication between financialinstitutions to facilitate real-time funds availability in paymenttransactions. The transaction system can be similar to system 110(FIG. 1) or system 203 (FIGS. 2-4). The payment and payment transactionscan be to pay one or more bills and/or other financial obligations.

In some embodiments, payment with real-time funds availability can beprovided through a consolidated payment model, such as shown in FIGS.10-14 and described below, where the payment model can be to pay one ormore bills or other financial obligations. For example, paymenttransactions can be initiated at an aggregator or consolidator website,such as, in some embodiments, at a website or an application of thesending participant, such as shown in FIGS. 13-14 and described below,or, in other embodiments, at a website or an application hosted by anapplication service provider that is separate from the sendingparticipant, such as shown in FIGS. 10-12 and described below. In manyembodiments, the application service provider can be separate from thesending participant, but the application service provider can host awebsite or an application on behalf of the sending participant. In anumber of embodiments, the consolidated payment model can allow theconsumer to make payments to multiple different billers. In someembodiments, the billers can be pre-registered to receive paymentsthrough the application service provider. In several embodiments,payment with real-time funds availability can be provided through abiller direct model, which can allow the sender to initiate paymenttransactions directly through a biller that issues bills, such asthrough a website or an application of the biller, such as shown inFIGS. 15-17 and described below.

Turning ahead in the drawings, FIGS. 10-12 illustrate block diagrams ofsystems that can be employed for real-time funds availability in paymenttransactions in a first exemplary scenario, using the consolidatedpayment model, in which an application service provider is separate fromthe sending participant. FIG. 10 illustrates a block diagram of a system1000 in which an application service provider 1030 is in datacommunication with a transaction system 1050, and showing messages foran “is account real-time capable call.” FIG. 11 illustrates a blockdiagram of system 1000, showing payment messages. FIG. 12 illustrates ablock diagram of a system 1200 that is a variation of system 1100 ofFIGS. 10-11, in which a sending participant 1040 is in datacommunication with application service provider 1030 instead oftransaction system 1050, and showing details of the payment messages.

System 1000 is merely exemplary and embodiments of the system are notlimited to the embodiments presented herein. The system can be employedin many different embodiments or examples not specifically depicted ordescribed herein. In some embodiments, certain elements or modules ofsystem 1000 can perform various procedures, processes, and/oractivities. In other embodiments, the procedures, processes, and/oractivities can be performed by other suitable elements or modules ofsystem 1000.

In many embodiments, system 1000 (FIGS. 10-11) can include a sender1010, a sender system 1020, application service provider 1030, sendingparticipant 1040, transaction system 1050, and/or receiving participant1060. In many embodiments, sender 1010 can be the payor of the bill-paytransaction (e.g., the customer) and/or can be an end-user thatinitiates a funds transfer, such as through sender system 1020. Inseveral embodiments, application service provider 1030 can be an entitythat provides a user interface (UI) or application programming interface(API) for a payment application 1031, which can be hosted by applicationservice provider and accessed through sender system 1020 and which canbe used to pay one or more bills and/or other financial obligations. Ina number of embodiments, sending participant 1040 can be a financialinstitution that holds a sender account 1041, which can be a fundingaccount of sender 1010 to be debited in conjunction with a debit/paymenttransaction. In many embodiments, sender participant 1040 can be similarto financial institutions 131-134 (FIG. 1), first financial institution202 (FIGS. 2-4) and/or second financial institution 204 (FIGS. 2-3). Inseveral embodiments, sending participant 1040 can approve a debit offunds from sending account 1041. Sender account 1041 can be the fundingaccount used by the sender to fund the transaction. In a number ofembodiments, sending participant 1040 can include a sending participantsettlement account 1042, which can be used by sending participant 1040to settle fund transfers between sending participant 1040 and otherfinancial institutions, such as receiving participant 1060.

In a number of embodiments, the application sponsor can be an entity orfinancial institution that approves the debit transactions from senderaccount 1041. In many embodiments, sending participant 1040 can serve asthe application sponsor for the network funds transfers for theconsolidated payment model, such as shown in FIGS. 10-14 and describedherein and below. In several embodiments, the receiving participant canserve as the application sponsor for the network funds transfers for thebiller direct model, such as shown in FIGS. 15-17 and described below.In a number of embodiments, receiving participant 1060 can be afinancial institution that holds a recipient account 1062 to be creditedin conjunction with the payment transaction. In many embodiments,receiving participant 1040 can be similar to financial institutions131-134 (FIG. 1), first financial institution 202 (FIGS. 2-4) and/orsecond financial institution 204 (FIGS. 2-3). In many embodiments, therecipient can be the biller, which can receive the funds in recipientaccount 1062 of receiving participant 1060, and/or can be an end-userwhose account is credited in conjunction with the payment transaction.In several embodiments, receiving participant 1060 can include a billingaccount 1061, which can be an account billed to sender 1010, and whichis used by sender 1010 to fund a bill-payment or funds transfer tobilling account 1061. In a number of embodiments, receiving participant1060 can include a receiving participant settlement account 1063, whichcan be used by receiving participant 1060 to settle fund transfersbetween receiving participant 1060 and other financial institutions,such as sending participant 1040.

In a number of embodiments, the payment transaction can include variousmessages between various elements of the system. In some embodiments,the messages can include messages for an “is account real-time capablecall,” which can determine whether real-time payment is an availableoption for the biller/recipient, such as shown in FIGS. 10, 13, and 15,and described below. In a number of embodiments, the messages caninclude payment messages, which can include providing a real-timepromise-to-pay to the receiving participant, such that the receivingparticipant can make funds available in real-time to thebiller/recipient, such as shown in FIGS. 11-12, 14, and 16-17, anddescribed below.

In the first exemplary scenario, as shown in FIGS. 10-12, a website canbe hosted by application service provider 1030, which can be separatefrom, but on behalf of, sending participant 1040. As an example, theapplication service provider can be Fiserv, Inc. (“Fiserv”), ofBrookfield, Wis. or another suitable application service provider;sending participant 1040 (and the application sponsor) can be CapitalOne Financial Corp. (“CapOne” or “Capital One”), of McLean, Va., oranother suitable sending participant; and receiving participant 1060 canbe United States Automotive Association Federal Savings Bank (“USAA”),of San Antonio, Tex., or another suitable receiving participant. In thisexemplary scenario, a Capital One customer, such as sender 1010, can usesender system 1020 to log onto a consolidated payment website, such aspayment application 1031, provided by Fisery to initiate a paymenttransaction to pay a USAA credit card (e.g., billing account 1061) froma Capital One account (e.g., sender account 1041). For example, Fiserycan provide a Fisery application to sender 1010, such as through awebsite accessed on sender system 1020. In many embodiments, applicationservice provider 1030 can include payment processor system 1032, such asthe NOW network of Fiserv, or another suitable payment processor system.Application service provider 1030 thus can be referred to as a paymentprocessor. In a number of embodiments, payment processor system 1032 caninclude at least one payment processor settlement account 1033, whichcan be an account that resides at a financial institution that is usedby application service provider 1030 to facilitate settlement with otherfinancial institutions. In some embodiments, application serviceprovider 1030 can include a payment processor settlement account 1033for each financial institution within a network of financialinstitutions that use application service provider 1030 for paymentprocessing.

In many embodiments, payment processor system 1032 of applicationservice provider 1030 can be in data communication with transactionsystem 1050. In some embodiments, transaction system 1050 can be aswitch and/or switch network provided by an entity separate from sendingparticipant 1040, receiving participant 1060, and/or application serviceprovider 1030, such as Early Warning Services, LLC, of Scottsdale,Ariz., or another suitable entity. In a number of embodiments,transaction system 1050 can be in data communication with receivingparticipant 1060, as shown in FIGS. 10-12. In some embodiments, sendingparticipant 1040 can be in data communication with transaction system1050, as shown in FIGS. 10-11. In other embodiments, sending participant1040 can be in data communication with application service provider1030, as shown in FIG. 12.

FIG. 10 illustrates messages for an “is account real-time capable call,”which can be used to determine if application service provider 1030should present an instant (real-time) payment option to sender 1010 forthe biller, by determining if the one or more relevant accounts (i.e.,sender account 1041 and recipient account 1062) are real-time capable.For example, sender 1010 can log onto Capital One's payment websitehosted by Fiserv, and the sender can choose to pay a bill for thebiller/recipient, which has an account with USAA. As shown in FIG. 10,in a number of embodiments, the request by sender 1010 to pay a billsent by the biller can cause sender system 1020 to send a message 1071to application service provider 1030 to determine if the relevantaccounts are real-time capable. Application service provider 1030 canreceive message 1071 from sender system 1020, and can forward message1071 in a message 1072 to transaction system 1050 to determine if therelevant accounts are real-time capable. Transaction system 1050 receivemessage 1072 from application service provider 1030, and can forwardmessage 1072 to receiving participant 1060 in a message 1073 todetermine if the relevant accounts are real-time capable. Receivingparticipant 1060 can receive message 1073 from transaction system 1050,can determine whether recipient account 1062 is capable of handlingreal-time funds availability transactions, and can send a response totransaction system 1050 in a message 1074, which can indicate whetherrecipient account 1062 is capable of handling real-time fundsavailability transactions. Transaction system 1050 can receive message1074 from receiving participant 1060, and can forward message 1072 in amessage 1075 to sending participant 1040 to determine if the relevantaccounts are real-time capable. Sending participant 1040 can receivemessage 1075 from transaction system 1050, can determine whether senderaccount 1041 is capable of handling real-time funds availabilitytransactions, and can send a response to transaction system 1050 in amessage 1076, which can indicate whether sender account 1041 is capableof handling real-time funds availability transactions. Transactionsystem 1050 can receive message 1076 from sending participant 1040. Insome embodiments, messages 1073 and 1075 can be sent from transactionsystem 1050 in any suitable order, and messages 1074 and 1076 can bereceived at transaction system 1050 in any suitable order.

Transaction system 1050 can forward the responses that were received bytransaction system 1050 in message 1074 and message 1076 to applicationservice provider 1030 in a message 1077. Application service provider1030 can receive message 1077 from transaction system 1050. If therelevant accounts are real-time capable, application service provider1030 can present an instant payment option to sender 1010 by sending amessage 1078 to sender system 1020. Sender system 1020 can receivemessage 1078 from application service provider 1030. If sendingparticipant 1040 is instead in data communication with applicationservice provider 1030 instead of transaction system 1050, applicationservice provider 1030 can communicate with sending participant 1040,instead of transaction system 1050 communicating with sendingparticipant 1040, to determine if sender account 1041 is capable ofhandling real-time funds availability transactions. In many embodiments,the “is account real-time capable call” messages (e.g., messages1071-1078) can each individually, and/or collectively, occur inreal-time.

FIG. 11 illustrates payment messages in system 1000, which is a firstversion of consolidated real-time payment using application serviceprovider 1030 separate from sending participant 1040, in which sendingparticipant 1040 is in data communication with transaction system 1050.As shown in FIG. 11, in a number of embodiments, sender 1010 can usesender system 1020 to submit payment in real-time to application serviceprovider 1030 in a message 1171. Application service provider 1030 canreceive message 1171 from sender system 1020, and can send a message1172 to transaction system 1050 to debit sender account 1041.Transaction system 1050 can receive message 1172 from applicationservice provider 1030, and can send a message 1173 to sendingparticipant 1040 to debit sender account 1041 in sending participant1040. Sending participant 1040 can receive message 1173 from transactionsystem 1050, can debit the funds for the payment from sender account1041 in an activity 1145, and can credit the funds to sendingparticipant settlement account 1042 in an activity 1146. In manyembodiments, sending participant 1040 can determine whether tosuccessfully debit sender account 1041 based on a number of factors,such as whether sender account 1041 is open and in good status (orclosed), whether sender account 1041 has had recent not sufficient funds(NSF) activity, whether sender account 1041 has a stop payment order,whether sender account 1041 has sufficient funds for the debit, and/orother suitable factors.

In several embodiments, once sending participant 1040 has successfullydebited sender account 1041, sending participant 1040 can send a message1174 to transaction system 1050 that the debit of sender account 1041was successful. Transaction system 1050 can receive message 1174 fromsending participant 1040, and can forward message 1174 to applicationservice provider 1030 in a message 1175 indicating that debiting ofsender account 1041 was successful. Application service provider 1030can receive message 1175 from transaction system 1050. Once applicationservice provider 1030 has determined that the debit of sender account1041 was successful, application service provider 1030 can send amessage 1176 to transaction system 1050 of a promise-to-pay credit.Transaction system 1050 can receive message 1176 from applicationservice provider 1030, and can forward message 1176 to receivingparticipant 1060 in a message 1177 of a promise-to-pay credit. Receivingparticipant 1060 can receive message 1177 from transaction system 1050,can credit the funds to recipient account 1062 in an activity 1165, andcan debit the funds from receiving participant settlement account 1063in an activity 1166, to provide real-time funds availability to thebiller/recipient. In many embodiments, when recipient account 1062 hasbeen credited, an accounts receivable (AR) system can credit the fundsto billing account 1061 corresponding to sender 1010 of thebiller/recipient in an activity 1167, which can indicate that sender1010 has paid billing account 1061.

In many embodiments, once receiving participant 1060 has successfullycredited recipient account 1062, receiving participant 1060 can send amessage 1178 to transaction system 1050 that the credit of recipientaccount 1062 was successful. Transaction system 1050 can receive message1178 from receiving participant 1060, and can forward message 1178 toapplication service provider 1030 in a message 1179 indicating that thecredit of recipient account 1062 was successful. Application serviceprovider 1030 can receive message 1179 from transaction system 1050, andcan present a notification of success to sender 1010 to sender system1020 in a message 1180 that the instant (real-time) payment wassuccessful. Sender system 1020 can receive message 1180 from applicationservice provider 1030, and can provide information to sender 1010 thatthe real-time payment was successful. In many embodiments, the paymentmessages (e.g., 1171-1180) can each individually, and/or collectively,occur in real-time.

In a number of embodiments, the settlement of funds in the variousaccounts (e.g., payment processor settlement account 1033, senderaccount 1041, sending participant settlement account 1042, billingaccount 1061, recipient account 1062, and receiving participantsettlement account 1063) can occur through various different channelsand or through various different methods. For example, in someembodiments, application service provider 1030 can act as a settlementagent, which can effectuate a pull automated clearinghouse (ACH) of thefunds from sending participant settlement account 1042 to paymentprocessor settlement account 1033 in an activity 1191. In manyembodiments, application service provider 1030 can effectuate a push ACHof the funds to receiving participant settlement account 1063 frompayment processor settlement account 1033 in an activity 1192. In otherembodiments, the settlement of funds can occur outside of applicationservice provider 1030. In some embodiments, the settlement oftransactions can occur nightly in batches, or occasionally during theday, such as 2-5 times a day. In other embodiments, as described below,the settlement of transactions can occur for each payment transaction orregularly for small groups of transactions. In some embodiments, thesettlement transactions can occur for each payment transaction inreal-time. Various embodiments of settlement are described below infurther detail.

In various first embodiments of settlement, settlement can occur as netsettlement with batch posting of financial accounts. In such firstembodiments of settlement, in activity 1145, sending participant 1040can apply the debit of funds from sender account 1041 in real-time forproviding a payment guarantee. In activity 1146, sending participant1040 can credit sending participant settlement account 1042 after senderaccount 1041 is debited. Sending participant settlement account 1042 canbe debited later when settlement completes, such as in activity 1191 ofpulling the funds from sending participant settlement account 1042 topayment processor settlement account 1033. In activity 1167, billingaccount 1061 can be updated in real-time to reflect the payment in thebalance and open-to-buy (OTB) amount of the USAA credit card, forexample. In activity 1165, receiving participant 1060 can apply a memopost credit to recipient account 1062 in real-time when receivingparticipant 1060 receives the promise-to-pay (e.g., message 1177).Recipient account 1062 can be credited later when receiving participantsettlement account 1063 is credited when settlement completes. Inactivity 1166, receiving participant 1060 can apply a memo post debit toreceiving participant settlement account 1063. Receiving participantsettlement account 1063 can be credited later when settlement completes.Settlement can complete when activities 1191 and 1192 occur, which canresult in transfer of funds from sending participant settlement account1042 to receiving participant settlement account 1063 through paymentprocessor settlement account 1033.

In the first embodiments of settlement, within real-time of sendersubmitting payment (e.g., in message 1171), payment can be visible asposted or pending, and the USAA credit card or line of credit OTB canreflect accepted payment with funds available to spend. The accountbalance for sender 1010 in billing account 1061 can reflect payment inreal-time upon receiving participant receiving the promise-to-pay (e.g.message 1177). Receiving participant settlement account 1063 can bedebited and credited for the amount of the payment when the funds arereceived in receiving participant settlement account 1063 whensettlement completes.

In the first embodiments of settlement, settlement can complete throughthe conventional ACH settlement process, such as intra-day or overnightbatch processing. In some of the first embodiments of settlement,settlement completion in activities 1191 and 1192 can occur as singleACH items for each transaction. For example, during the batch posting atsettlement completion, each transaction can be represented as a singleACH item. In others of the first embodiments of settlement, multipletransactions can be batched and represented as single transaction. Forexample, if there are multiple transactions between the same twofinancial institutions, those transactions can all be batched togetherand settled as a single batch ACH, or through a wire advice file.

In various second embodiments of settlement, settlement can occur as netsettlement with batch posting of financial accounts with real-timeposting of the AR system. Such second embodiments of settlement can besimilar to the first embodiments of settlement. For example, in activity1145, sending participant 1040 can apply the debit of funds from senderaccount 1041 in real-time for providing a payment guarantee. In activity1146, sending participant 1040 can credit sending participant settlementaccount 1042 after sender account 1041 is debited. Sending participantsettlement account 1042 can be debited later when settlement completes,such as in activity 1191 of pulling the funds from sending participantsettlement account 1042 to payment processor settlement account 1033. Inactivity 1167, billing account 1061 can be updated in real-time toreflect the payment in the balance and open-to-buy (OTB) amount of theUSAA credit card, for example. In activity 1166, receiving participant1060 can apply a memo post debit to receiving participant settlementaccount 1063. Receiving participant settlement account 1063 can becredited later when settlement completes. Settlement can complete whenactivities 1191 and 1192 occur, which can result in transfer of fundsfrom sending participant settlement account 1042 to receivingparticipant settlement account 1063 through payment processor settlementaccount 1033.

The second embodiments of settlement can be different from the firstembodiments of settlement in some respects. For example, in activity1165, receiving participant 1060 can update recipient account 1062 toapply a hard credit in real-time after receiving participant 1060receives the promise-to-pay (e.g., message 1177). Recipient account 1062can be credited from receiving participant settlement account 1063.

In the second embodiments of settlement, within real-time of sendersubmitting payment (e.g., in message 1171), payment can be visible asposted (not pending), and the USAA credit card or line of credit OTB canreflect accepted payment with funds available to spend. The accountbalance for sender 1010 in billing account 1061 can be updated inreal-time upon receiving participant receiving the promise-to-pay (e.g,message 1177), and recipient account 1062 can be credited in real-time.Receiving participant settlement account 1063 can be debited inreal-time for the amount of the payment transferred to recipient account1062, and can be credited for the amount of the payment when the fundsare received in receiving participant settlement account 1063 whensettlement completes.

The second embodiments of settlement can be similar to the firstembodiments of settlement for completion of settlement. For example,settlement can complete through the conventional ACH settlement process,such as intra-day or overnight batch processing. In some of the secondembodiments of settlement, settlement completion in activities 1191 and1192 can occur as single ACH items for each transaction. For example,during the batch posting at settlement completion, each transaction canbe represented as a single ACH item. In others of the second embodimentsof settlement, multiple transactions can be batched and represented assingle transaction. For example, if there are multiple transactionsbetween the same two financial institutions, those transactions can allbe batched together and settled as a single batch ACH, or through a wireadvice file.

In various third embodiments of settlement, settlement can occur asreal-time settlement and real-time posting to the financial accounts andthe AR system. Such third embodiments of settlement can be similar tothe second embodiments of settlement. For example, in activity 1145,sending participant 1040 can apply the debit of funds from senderaccount 1041 in real-time for providing a payment guarantee. In activity1167, billing account 1061 can be updated in real-time to reflect thepayment in the balance and open-to-buy (OTB) amount of the USAA creditcard, for example. In activity 1165, receiving participant 1060 canupdate recipient account 1062 to apply a hard credit in real-time afterreceiving participant 1060 receives the promise-to-pay (e.g., message1177). Recipient account 1062 can be credited from receiving participantsettlement account 1063.

The third embodiments of settlement can be different from the secondembodiments of settlement in some respects. For example, in activity1146, sending participant 1040 can credit in real-time when senderaccount 1041 is debited, and can debit sending participant settlementaccount 1042 in real-time through settlement that completes in real-timeafter sender 1010 initiates the payment (e.g., in message 1171). Inactivity 1166, receiving participant 1060 can apply a debit in real-timeto receiving participant settlement account 1063. Receiving participantsettlement account 1063 can be credited in real-time through settlementthat completes in real-time after sender 1010 initiates the payment(e.g., in message 1171).

In the third embodiments of settlement, within real-time of sendersubmitting payment (e.g., in message 1171), payment can be visible asposted (not pending), and the USAA credit card or line of credit OTB canreflect accepted payment with funds available to spend. The accountbalance for sender 1010 in billing account 1061 can be updated inreal-time upon receiving the promise-to-pay (e.g., message 1177), andrecipient account 1062 can be credited in real-time. Receivingparticipant settlement account 1063 can be debited in real-time for theamount of the payment transferred to recipient account 1062, and can becredited in real-time for the amount of the payment as the funds arereceived in real-time receiving participant settlement account 1063.

The third embodiments of settlement can be different from the first andsecond embodiments of settlement for completion of settlement. In thethird embodiments of settlement, real-time settlement can completethrough a process that transfers funds from sending participantsettlement account 1042 to receiving participant settlement account 1063in real-time for each transaction. In some embodiments, real-timesettlement completion of funds from sending participant settlementaccount 1042 to receiving participant settlement account 1063 can occurthrough payment processor settlement account 1033, through transactionsystem 1050, or through another suitable funds transfer mechanism.

In some of the third embodiments of settlement, activities 1191 and 1192can occur after activity 1146 and before activity 1166. In otherembodiments, activities 1191 and 1192 can occur after activities 1146and 1166.

FIG. 11 illustrates payment messages in system 1000, which is a firstversion of consolidated real-time payment using application serviceprovider 1030 separate from sending participant 1040, in which sendingparticipant 1040 is in data communication with transaction system 1050.

FIG. 12 illustrates payment messages in a system 1200, which is a secondversion of consolidated real-time payment using application serviceprovider 1030 separate from sending participant 1040, in which sendingparticipant 1040 is in data communication with application serviceprovider 1030, instead of sending participant 1040 being in datacommunication with transaction system 1050. System 1200 is merelyexemplary and embodiments of the system are not limited to theembodiments presented herein. The system can be employed in manydifferent embodiments or examples not specifically depicted or describedherein. In some embodiments, certain elements or modules of system 1200can perform various procedures, processes, and/or activities. In otherembodiments, the procedures, processes, and/or activities can beperformed by other suitable elements or modules of system 1200.

In many embodiments, system 1200 can include sender 1010, sender system1020, application service provider 1030, sending participant 1040,transaction system 1050, and/or receiving participant 1060, as describedabove in connection with FIGS. 10-11, but sending participant 1040 canbe in data communication with application service provider 1030 insteadof transaction system 1050, as shown in FIG. 12.

As shown in FIG. 12, in a number of embodiments, sender 1010 can usesender system 1020 to submit payment in real-time to application serviceprovider 1030 in a message 1271. Message 1271 can be similar oridentical to message 1171 (FIG. 11). Application service provider 1030can receive message 1271 from sender system 1020, and can send a message1272 to sending participant 1040 to debit sender account 1041. Sendingparticipant 1040 can receive message 1272 from application serviceprovider 1030, can debit the funds for the payment from sender account1041 in activity 1145, and can credit the funds to sending participantsettlement account 1042 in activity 1146, as described above inconnection with FIG. 11. In several embodiments, once sendingparticipant 1040 has successfully debited sender account 1041, sendingparticipant 1040 can send a message 1273 to application service provider1030 indicating that the debit of sender account 1041 was successful.Application service provider 1030 can receive message 1273 from sendingparticipant 1040.

Once application service provider 1030 has determined that the debit ofsender account 1041 was successful, application service provider 1030can send a message 1274 to transaction system 1050 of a promise-to-paycredit. Transaction system 1050 can receive message 1274 fromapplication service provider 1030, and can forward message 1274 toreceiving participant 1060 in a message 1275 of a promise-to-pay credit.Receiving participant 1060 can receive message 1275 from transactionsystem 1050, can credit the funds to recipient account 1062 in activity1165, and can debit the funds from receiving participant settlementaccount 1063 in activity 1166, to provide real-time funds availabilityto the biller/recipient, as described above in connection with FIG. 11.In many embodiments, when recipient account 1062 has been credited, theaccounts receivable (AR) system can credit the funds to billing account1061 corresponding to sender 1010 of the biller/recipient in activity1167, which can indicate that sender 1010 has paid billing account 1061,as described above in connection with FIG. 11.

In many embodiments, once receiving participant 1060 has successfullycredited recipient account 1062, receiving participant 1060 can send amessage 1276 to transaction system 1050 that the credit of recipientaccount 1062 was successful. Transaction system 1050 can receive message1276 from receive participant 1060, and can forward message 1276 toapplication service provider 1030 in a message 1277 indicating that thecredit of recipient account 1062 was successful. Application serviceprovider 1030 can receive message 1277 from transaction system 1050, andcan present a notification of success to sender 1010 to sender system1020 in a message 1278 that the instant (real-time) payment wassuccessful. Sender system 1020 can receive message 1278 from applicationservice provider 1030, and can provide information to sender 1010 thatthe real-time payment was successful. In many embodiments, the paymentmessages (e.g., 1271-1278) can each individually, and/or collectively,occur in real-time.

In a number of embodiments, the settlement of funds in the variousaccounts (e.g., sender account 1041, sending participant settlementaccount 1042, billing account 1061, recipient account 1062, andreceiving participant settlement account 1063) can be identical to thevarious embodiments described above in connection with FIG. 11.

Turning ahead in the drawings, FIGS. 13-14 illustrate block diagrams ofa system that can be employed for real-time funds availability inpayment transactions in a second exemplary scenario, using theconsolidated payment model, in which the application service provider isthe same as the sending participant. FIG. 13 illustrates a block diagramof a system 1300, showing messages for an “is account real-time capablecall.” FIG. 14 illustrates a block diagram of system 1300, showingdetails of the payment messages.

System 1300 is merely exemplary and embodiments of the system are notlimited to the embodiments presented herein. The system can be employedin many different embodiments or examples not specifically depicted ordescribed herein. In some embodiments, certain elements or modules ofsystem 1300 can perform various procedures, processes, and/oractivities. In other embodiments, the procedures, processes, and/oractivities can be performed by other suitable elements or modules ofsystem 1300.

In many embodiments, system 1300 (FIGS. 13-14) can include a sender1010, a sender system 1020, an application service provider 1330,sending participant 1040, transaction system 1050, and/or receivingparticipant 1060. In several embodiments, application service provider1330 can be an entity that provides a user interface (UI) or applicationprogramming interface (API) for payment application 1031, in whichapplication service provider 1530 and/or payment application 1531 areproprietary to sending participant 1040.

In the second exemplary scenario, as shown in FIG. 13-14, sendingparticipant 1040 can provide a payment application 1331 to sender 1010.Similar to other payment applications described above, paymentapplication 1331 can be used to pay one or more bills and/or otherfinancial obligations. For example, sending participant 1040,application service provider 1330, and the application sponsor can beWells Fargo & Co. (“Wells Fargo”), of San Francisco, Calif.; andreceiving participant 1060 can be USAA. In this exemplary scenario, aWells Fargo customer, such as sender 1010, can use sender system 1020 tolog onto a consolidated payment website, such as payment application1331, hosted by Wells Fargo to pay a USAA auto loan (e.g., billingaccount 1061) from a demand deposit account (DDA) (e.g., sender account1041) of the customer (e.g., sender 1010) at Wells Fargo. In variousembodiments, sending participant 1040 can provide payment application1331, which can be accessed by sender 1010 to initiate a paymenttransaction. For example, Wells Fargo can provide a website. In manyembodiments, sending participant 1040 can be in data communication withtransaction system 1050. In a number of embodiments, transaction system1050 can be in data communication with receiving participant 1060, asshown in FIGS. 13-14. Application service provider 1330 and paymentapplication 1331 can be part of sending participant 1040, and can be indata communication with each other.

FIG. 13 illustrates messages for an “is account real-time capable call,”which can be used to determine if application service provider 1330should present an instant (real-time) payment option to sender 1010 forthe biller, by determining if the one or more relevant accounts (i.e.,sender account 1041 and recipient account 1062) are real-time capable.The “is account real-time capable call” in FIG. 13 can be similar to the“is account real-time capable call” in FIG. 10. But unlike the “isaccount real-time capable call” of FIG. 10, the “is account real-timecapable call” in FIG. 13 is modified because application serviceprovider 1330 is not separate from sending participant 1040. Becauseapplication service provider 1330 and sending participant 1040 are thesame entity, sending participant 1040/application service provider 1330can know when sender account 1041 at sending participant 1040 isreal-time capable, so it is not necessary to send a message to sendingparticipant 1040 to determine if sender account 1041 is real-timecapable.

As shown in FIG. 13, in a number of embodiments, the request by sender1010 to pay a bill sent by the biller can cause sender system 1020 tosend a message 1371 to application service provider 1330 to determine ifthe relevant accounts are real-time capable. Application serviceprovider 1330 can receive message 1371 from sender system 1020, and canforward message 1371 to transaction system 1050 in a message 1372 todetermine if the relevant accounts are real-time capable. Transactionsystem 1050 can receive message 1372 from application service provider1330, and can forward message 1372 to receiving participant 1060 in amessage 1373 to determine if the relevant accounts are real-timecapable. Receiving participant 1060 can receive message 1373 fromtransaction system 1050, can determine whether recipient account 1062 iscapable of handling real-time funds availability transactions, and cansend a response to transaction system 1050 in a message 1374, which canindicate whether recipient account 1062 is capable of handling real-timefunds availability transactions.

Transaction system 1050 can receive message 1374 from receivingparticipant 1060, and can forward the response in message 1374 toapplication service provider 1330 in a message 1375 indicating whetherrecipient account 1062 is capable of handling real-time fundsavailability transactions. Application service provider 1330 can receivemessage 1375 from transaction system 1050. As explained above,application service provider 1330 can know whether sender account 1041is real-time capable. If the relevant accounts are real-time capable,application service provider 1330 can present an instant payment optionto sender 1010 by sending a message 1376 to sender system 1020. Sendersystem 1020 can receive message 1376 from application service provider1030. In many embodiments, the “is account real-time capable call”messages (e.g., messages 1371-1376) can each individually, and/orcollectively, occur in real-time.

FIG. 14 illustrates payment messages in system 1300. As shown in FIG.14, in a number of embodiments, sender 1010 can use sender system 1020to submit payment in real-time to application service provider 1330 in amessage 1471. Message 1471 can be similar or identical to message 1171(FIG. 11) and/or message 1271 (FIG. 12). Application service provider1330 can receive message 1471 from sender system 1020, and can send amessage 1472 internally to sending participant 1040 to debit senderaccount 1041. Sending participant 1040 can receive message 1472 fromapplication service provider 1330, and can debit the funds for thepayment from sender account 1041 in activity 1145 and credit the fundsto sending participant settlement account 1042 in activity 1146, asdescribed above in connection with FIG. 11. In several embodiments, oncesending participant 1040 has successfully debited sender account 1041,sending participant 1040 can send a message 1473 internally toapplication service provider 1330 indicating that the debit of senderaccount 1041 was successful. Application service provider 1330 canreceive message 1473 from sending participant 1040.

In several embodiments, once application service provider 1330 hasdetermined that the debit of sender account 1041 was successful,application service provider 1330 can send a message 1474 to transactionsystem 1050 of a promise-to-pay credit. Transaction system 1050 canreceive message 1474 from application service provider 1330, and canforward message 1474 to receiving participant 1060 in a message 1475 ofa promise-to-pay credit. Receiving participant 1060 can receive message1475 from transaction system 1050, credit the funds to recipient account1062 in activity 1165, and can debit the funds from receivingparticipant settlement account 1063 in activity 1166, to providereal-time funds availability to the biller/recipient, as described abovein connection with FIG. 11. In many embodiments, when recipient account1062 has been credited, the AR system can credit the funds to billingaccount 1061 corresponding to sender 1010 of the biller/recipient inactivity 1167, which can indicate that sender 1010 has paid billingaccount 1061, as described above in connection with FIG. 11.

In many embodiments, once receiving participant 1060 has successfullycredited recipient account 1062, receiving participant 1060 can send amessage 1476 to transaction system 1050 that the credit of recipientaccount 1062 was successful. Transaction system 1050 can receive message1476 from receive participant 1060, and can forward message 1476 toapplication service provider 1330 in a message 1477 indicating that thecredit of recipient account 1062 was successful. Application serviceprovider 1330 can receive message 1477 from transaction system 1050, andcan present a notification of success to sender 1010 to sender system1020 in a message 1478 that the instant (real-time) payment wassuccessful. Sender system 1020 can receive message 1478 from applicationservice provider 1330, and can provide information to sender 1010 thatthe real-time payment was successful. In many embodiments, the paymentmessages (e.g., 1471-1478) can each individually, and/or collectively,occur in real-time.

In a number of embodiments, the settlement of funds in the variousaccounts (e.g., sender account 1041, sending participant settlementaccount 1042, billing account 1061, recipient account 1062, andreceiving participant settlement account 1063) can be similar to thevarious embodiments described above in connection with FIG. 11, exceptthat activities 1191 and 1192 can be replaced with an activity 1491 thatdoes not involve payment processor settlement account 1033 (FIGS.10-12). The first and second embodiments of settlement described abovein connection with FIG. 11 can be modified such that activity 1491 caninclude a single ACH item for each transaction (such as an ACH push fromsending participant settlement account 1042 to receiving participantsettlement account 1063, or, alternatively, an ACH pull from receivingparticipant settlement account 1063 from sending participant settlementaccount 1042), or a batched transactions, such that if there aremultiple transactions between the same two financial institutions, thosetransactions can all be batched together and settled as a single batchACH, or through a wire advice file. The third embodiments of settlementdescribed above in connection with FIG. 11 can be modified such thatactivity 1491 can include real-time settlement that can complete througha process that transfers funds from sending participant settlementaccount 1042 to receiving participant settlement account 1063 inreal-time for each transaction after the payment has been initiated. Insome of the third embodiments of settlement, activity 1491 can occurafter activity 1146 and before activity 1166. In other embodiments,activity 1491 can occur after activities 1146 and 1166. In someembodiments, real-time settlement completion of funds from sendingparticipant settlement account 1042 to receiving participant settlementaccount 1063 can occur through transaction system 1050, or throughanother suitable funds transfer mechanism.

Turning ahead in the drawings, FIGS. 15-17 illustrate block diagrams ofsystems that can be employed for real-time funds availability in paymenttransactions in a third exemplary scenario, using the biller directmodel, in which the application service provider is the same entity asthe receiving participant. FIG. 15 illustrates a block diagram of asystem 1500, in which receiving participant 1060 is in datacommunication with transaction system 1050 for credit call messages, andshowing messages for an “is account real-time capable call.” FIG. 16illustrates a block diagram of system 1500, showing the paymentmessages. FIG. 17 illustrates a block diagram of a system 1700 that is avariation of system 1500 of FIGS. 15-16, in which receiving participant1060 is in data communication for the credit call messages with anapplication service provider 1530 instead of transaction system 1050,and showing the payment messages.

System 1500 is merely exemplary and embodiments of the system are notlimited to the embodiments presented herein. The system can be employedin many different embodiments or examples not specifically depicted ordescribed herein. In some embodiments, certain elements or modules ofsystem 1500 can perform various procedures, processes, and/oractivities. In other embodiments, the procedures, processes, and/oractivities can be performed by other suitable elements or modules ofsystem 1500.

In many embodiments, system 1500 (FIGS. 15-16) can include a sender1010, a sender system 1020, an application service provider 1530,sending participant 1040, transaction system 1050, and/or receivingparticipant 1060. In several embodiments, application service provider1530 can be an entity that provides a user interface (UI) or applicationprogramming interface (API) for payment application 1031, in whichapplication service provider 1530 and/or a payment application 1531 areproprietary to receiving participant 1060.

In the third exemplary scenario, as shown in FIG. 15-17, receivingparticipant 1060 can provide payment application 1531 to sender 1010.Similar to other payment applications described above, paymentapplication 1531 can be used to pay one or more bills and/or otherfinancial obligations. For example, receiving participant 1060 andapplication service provider 1530 can be Capital One, and sendingparticipant 1040 can be USAA. In this exemplary scenario, a Capital Onecustomer, such as sender 1010, can use sender system 1020 to log onto adirect payment website, such as payment application 1531 from CapitalOne to pay the customer's Capital One credit card (e.g., billing account1061) from a DDA account held by the customer at USAA (e.g., senderaccount 1041). In various embodiments, receiving participant 1060 canprovide payment application 1531, which can be accessed by sender 1010to initiate a payment transaction. For example, Capital One can providea billing application layer, such as a website or an application (e.g.,mobile application). In many embodiments, application service provider1530 can be in data communication with transaction system 1050. In anumber of embodiments, transaction system 1050 can be in datacommunication with sending participant 1040. In many embodiments,application service provider 1530 can have an internal datacommunication link with receiving participant 1060. In some embodiments,promise-to-pay credit call messages can be sent to and received fromreceiving participant 1060 through transaction system 1050, such asshown in FIG. 16 and described below. In other embodiments,promise-to-pay credit call messages can be sent to and received fromreceiving participant 1060 through application service provider 1530, asshown in FIG. 17 and described below.

FIG. 15 illustrates messages for an “is account real-time capable call,”which can be used to determine if application service provider 1530should present an instant (real-time) payment option to sender 1010 forthe biller, by determining if the one or more relevant accounts (i.e.,sender account 1041 and recipient account 1062) are real-time capable.The “is account real-time capable call” in FIG. 15 can be similar to the“is account real-time capable call” in FIGS. 10 and 13. But unlike the“is account real-time capable call” of FIGS. 10 and 13, the “is accountreal-time capable call” in FIG. 15 is modified because applicationservice provider 1530 is not separate from receiving participant 1060.Because application service provider 1530 and receiving participant 1040are the same entity, receiving participant 1060/application serviceprovider 1530 can know when recipient account 1062 at receivingparticipant 1060 is real-time capable, so it can be not necessary tosend a message to receiving participant 1060 to determine if recipientaccount 1062 is real-time capable.

As shown in FIG. 15, in a number of embodiments, the request by sender1010 to pay a bill sent by the biller can cause sender system 1020 tosend a message 1571 to application service provider 1530 to determine ifthe relevant accounts are real-time capable. Application serviceprovider 1530 can receive message 1571 from sender system 1020, and canforward message 1571 to transaction system 1050 in a message 1572 todetermine if the relevant accounts are real-time capable. Transactionsystem 1050 can receive message 1572 from application service provider1530, and can forward message 1572 to sending participant 1040 in amessage 1573 to determine if the relevant accounts are real-timecapable. Sending participant 1040 can receive message 1573 fromtransaction system 1050, can determine whether sender account 1041 iscapable of handling real-time funds availability transactions, and cansend a response to transaction system 1050 in a message 1574, which canindicate whether sending account 1041 is capable of handling real-timefunds availability transactions.

Transaction system 1050 can receive message 1574 from sendingparticipant 1040, and can forward the response in message 1574 toapplication service provider 1530 in a message 1575 indicating whethersending account 1041 is capable of handling real-time funds availabilitytransactions. Application service provider 1530 can receive message 1575from transaction system 1050. As explained above, application serviceprovider 1530 can know whether recipient account 1062 is real-timecapable. If the relevant accounts are real-time capable, applicationservice provider 1530 can present an instant payment option to sender1010 by sending a message 1576 to sender system 1020. Sender system 1020can receive message 1576 from application service provider 1030. In manyembodiments, the “is account real-time capable call” messages (e.g.,messages 1571-1576) can each individually, and/or collectively, occur inreal-time.

FIG. 16 illustrates payment messages in system 1500, which is a firstversion of the biller direct model of real-time bill pay, in which theapplication service provider is the same entity as the receivingparticipant, and in which promise-to-pay credit call messages can besent to and received from receiving participant 1060 through transactionsystem 1050. As shown in FIG. 16, in a number of embodiments, sender1010 can use sender system 1020 to submit payment in real-time toapplication service provider 1530 in a message 1671. Application serviceprovider 1530 can receive message 1671 from sender system 1020, and cansend a message 1672 to transaction system 1050 to debit sender account1041. Transaction system 1050 can receive message 1672 from applicationservice provider 1530, and can send a message 1673 to sendingparticipant 1040 to debit sender account 1041 in sending participant1040. Sending participant 1040 can receive message 1673 from transactionsystem 1050, can debit the funds for the payment from sender account1041 in activity 1145, and can credit the funds to sending participantsettlement account 1042 in activity 1146, as described above inconnection with FIG. 11.

In several embodiments, once sending participant 1040 has successfullydebited sender account 1041, sending participant 1040 can send a message1674 to transaction system 1050 that the debit of sender account 1041was successful. Transaction system 1050 can receive message 1674 fromsending participant 1040, and can forward message 1674 to applicationservice provider 1530 in a message 1675 indicating that debiting ofsender account 1041 was successful. Application service provider 1530can receive message 1675 from transaction system 1050. Once applicationservice provider 1530 has determined that the debit of sender account1041 was successful, application service provider 1530 can send amessage 1676 to transaction system 1050 of a promise-to-pay credit.Transaction system 1050 can receive message 1676 from applicationservice provider 1530, and can forward message 1676 to receivingparticipant 1060 in a message 1677 of a promise-to-pay credit. Receivingparticipant 1060 can receive message 1677 from transaction system 1050,can credit the funds to recipient account 1062 in activity 1165, and candebit the funds from receiving participant settlement account 1063 inactivity 1166, to provide real-time funds availability to thebiller/recipient, as described above in connection with FIG. 11. In manyembodiments, when recipient account 1062 has been credited, the ARsystem can credit the funds to billing account 1061 corresponding tosender 1010 of the biller/recipient in activity 1167, which can indicatethat sender 1010 has paid billing account 1061, as described above inconnection with FIG. 11.

In many embodiments, once receiving participant 1060 has successfullycredited recipient account 1062, receiving participant 1060 can send amessage 1678 to transaction system 1050 that the credit of recipientaccount 1062 was successful. Transaction system 1050 can receive message1678 from receiving participant 1060, and can forward the response inmessage 1678 to application service provider 1530 in a message 1679indicating that the credit of recipient account 1062 was successful.Application service provider 1530 can receive message 1679 fromtransaction system 1050, and can present a notification of success tosender 1010 to sender system 1020 in a message 1680 that the instant(real-time) payment was successful. Sender system 1020 can receivemessage 1680 from application service provider 1530, and can provideinformation to sender 1010 that the real-time payment was successful. Inmany embodiments, the payment messages (e.g., 1671-1680) can eachindividually, and/or collectively, occur in real-time.

In a number of embodiments, the settlement of funds in the variousaccounts (e.g., sender account 1041, sending participant settlementaccount 1042, billing account 1061, recipient account 1062, andreceiving participant settlement account 1063) can be similar oridentical to the various embodiments described above in connection withactivity 1491 of FIG. 14.

FIG. 17 illustrates payment messages in system 1700, which is a secondversion of the biller direct model of real-time bill pay, in which theapplication service provider is the same entity as the receivingparticipant, and promise-to-pay credit call messages can be sent to andreceived from receiving participant 1060 through application serviceprovider 1530.

System 1700 is merely exemplary and embodiments of the system are notlimited to the embodiments presented herein. The system can be employedin many different embodiments or examples not specifically depicted ordescribed herein. In some embodiments, certain elements or modules ofsystem 1700 can perform various procedures, processes, and/oractivities. In other embodiments, the procedures, processes, and/oractivities can be performed by other suitable elements or modules ofsystem 1700.

In many embodiments, system 1700 can include sender 1010, sender system1020, application service provider 1530, sending participant 1040,transaction system 1050, and/or receiving participant 1060, as describedabove in connection with FIGS. 15-16, but promise-to-pay credit callmessages can be sent to and received from receiving participant 1060through application service provider 1530 instead of transaction system1050.

As shown in FIG. 17, in a number of embodiments, sender 1010 can usesender system 1020 to submit payment in real-time to application serviceprovider 1530 in a message 1771. Application service provider 1530 canreceive message 1771 from sender system 1020, and can send a message1772 to transaction system 1050 to debit sender account 1041.Transaction system 1050 can receive message 1772 from applicationservice provider 1530, and can send a message 1773 to sendingparticipant 1040 to debit sender account 1041 in sending participant1040. Sending participant 1040 can receive message 1773 from sendingparticipant 1040, can debit the funds for the payment from senderaccount 1041 in activity 1145, and can credit the funds to sendingparticipant settlement account 1042 in activity 1146, as described abovein connection with FIG. 11.

In several embodiments, once sending participant 1040 has successfullydebited sender account 1041, sending participant 1040 can send a message1774 to transaction system 1050 that the debit of sender account 1041was successful. Transaction system 1050 can receive message 1774 fromsending participant 1040, and can forward message 1774 to applicationservice provider 1530 in a message 1775 indicating that debiting ofsender account 1041 was successful. Application service provider 1530can receive message 1775 from transaction system 1050. Once applicationservice provider 1530 has determined that the debit of sender account1041 was successful, application service provider 1530 can send amessage 1776 to receiving participant 1060 of a promise-to-pay credit.Receiving participant 1060 can receive message 1776 from applicationservice provider 1530, can credit the funds to recipient account 1062 inactivity 1165, and can debit the funds from receiving participantsettlement account 1063 in activity 1166, to provide real-time fundsavailability to the biller/recipient, as described above in connectionwith FIG. 11. In many embodiments, when recipient account 1062 has beencredited, the AR system can credit the funds to billing account 1061corresponding to sender 1010 of the biller/recipient in activity 1167,which can indicate that sender 1010 has paid billing account 1061, asdescribed above in connection with FIG. 11.

In many embodiments, once receiving participant 1060 has successfullycredited recipient account 1062, receiving participant 1060 can send amessage 1777 to application service provider 1530, indicating that thecredit of recipient account 1062 was successful. Application serviceprovider 1530 can receive message 1777 from receiving participant 1060,and can present a notification of success to sender 1010 to sendersystem 1020 in a message 1778 that the instant (real-time) payment wassuccessful. Sender system 1020 can receive message 1778 from applicationservice provider 1530, and can provide information to sender 1010 thatthe real-time payment was successful. In many embodiments, the paymentmessages (e.g., 1771-1778) can each individually, and/or collectively,occur in real-time.

In a number of embodiments, the settlement of funds in the variousaccounts (e.g., sender account 1041, sending participant settlementaccount 1042, billing account 1061, recipient account 1062, andreceiving participant settlement account 1063) can be similar oridentical to the various embodiments described above in connection withactivity 1491 of FIG. 14.

In some embodiments, the “is account real-time capable call” in FIGS.10, 13, and/or 15 can validate real-time capability of accounts fromboth sending participant 1040 (FIGS. 10-17) and receiving participant1060 (FIGS. 10-17). In some embodiments, the “is account real-timecapable call” can determine whether the instant pay option should bepresented to the sender 1010 (FIGS. 10-17) on the payment application(e.g., 1031 (FIGS. 10-12), 1331 (FIGS. 13-14), and/or 1531 (FIGS.15-17)). The “is account real-time capable call” can verify if thefunding account and/or the biller account is real-time capable.

In many embodiments, the “is account real-time capable call” in FIGS.10, 13, and/or 15 advantageously can facilitate one or more of thefollowing benefits, among other benefits:

-   -   a. Account validation for real-time capability: Financial        institutions (e.g., sending participant 1040 (FIGS. 10-17)        and/or receiving participant 1060 (FIGS. 10-17)) or the        application service provider (e.g., 1030 (FIGS. 10-12), 1330        (FIGS. 13-14), and/or 1530 (FIG. 15-17) can initiate an accounts        capable call in order to validate whether or not sender account        1041 (FIGS. 10-17), billing account 1061 (FIG. 10-17), and/or        recipient account 1062 (FIGS. 10-17)) are real-time capable.    -   b. Settlement instructions from billers: The “is account        real-time capable call” response messages can be designed to        carry settlement information from the biller to sending        participant 1040, so that the messaging process can rely on        real-time information instead of expensive directory look-ups to        facilitate the remittance process. Providing the settlement        instructions during the initial capability call can        advantageously facilitate settlement participant 1040 not having        to rely on an older directory of accounts and the assurance that        the settlement account is the correct account.    -   c. Inform sender 1010 (FIGS. 10-17) of Settlement Expectations:        The message structure can incorporate a customer settlement        field where key values can be interpreted into formatted        messages back to the consumer in a real-time fashion. This can        provide information on settlement expectations and so forth. For        example, the biller can inform the customer (e.g., sender 1010        (FIGS. 10-17)) that payment will be accepted real-time and the        OTB in the billing account (e.g., billing account 1061 (FIGS.        10-17)) for the customer (e.g., sender 1010 (FIGS. 10-17)) will        be increased, but that the payment may not be visible on the        customer's statement for two business days (depending on the        settlement type used).    -   d. Optional billing account information: The “is account        real-time capable call” response messages can include optional        fields such as current balance, last payment date, minimum        amount due, and if provided, it can be displayed to the consumer        (e.g., sender 1010 (FIGS. 10-17)) on the Payment UI (user        interface) (e.g., payment application 1031 (FIGS. 10-12), 1331        (FIGS. 13-14), and/or 1531 (FIGS. 15-17)) at the time of        payment, which can provide beneficial information to sender 1010        (FIGS. 10-17).

In several embodiments, the “is account real-time capable call” caninclude various elements in the inquiry messages (e.g., messages1071-1073, 1075 (FIG. 10), 1371-1373 (FIG. 13), and/or messages1571-1573 (FIG. 15)), such as:

-   -   a. Message wrapper fields: This section of the inquiry message        can include fields, such as transaction ID, transaction date and        so forth.    -   b. Debit block: This section of the inquiry message can provide        information on the Funding Accounts. Data elements can be        include ABA, account number, etc.    -   c. Payment item block: This section of the inquiry message can        provide information on the item (e.g., on a credit card payment)        for which sender 1010 (FIGS. 10-17) wishes to make a payment.        Data elements can include billing account information,        personally identifiable information (PII) of sender 1010 (FIGS.        10-17) such as a name, a home address, a telephone number, a        social security number, a tax identification number, an age, an        income level, marital status, a number of dependents, a frequent        shopper identifier, shopping preferences, billing ID, etc.    -   d. Settlement block: This section of the inquiry message can        provide the information regarding sending participant settlement        account 1042 (FIGS. 10-17). Data elements can include account        information such as ABA and account number.

In several embodiments, the “is account real-time capable call” caninclude various elements in the response messages (e.g., messages 1074,1076-1078 (FIG. 10), 1374-1376 (FIG. 13), and/or messages 1574-1576(FIG. 15)), such as:

-   -   a. Message wrapper fields: This section of the response message        can include fields, such as transaction ID, transaction Date,        etc.    -   b. Debit block: This section of the response message can return        fields from sending participant 1040 (FIGS. 10-17) that        maintains sender account 1041 (FIGS. 10-17) for sender 1010        (FIGS. 10-17). Data elements can include: a real-time capable        flag, reason codes if account is not real-time capable, optional        fee information, etc.    -   c. Payment item block: This section of the response message can        return fields from receiving participant 1060 (FIGS. 10-17),        which in some instances can be the biller. Data elements can        include a real-time capable flag, reason codes if account is not        real-time capable, a customer messaging field, payment        information fields, and optional fee information field.    -   d. Settlement block: This section of the response message can        return fields from receiving participant 1060 (FIGS. 10-17),        which in some instances can be the biller. Data elements can        include information about receiving participant settlement        account 1063 (FIGS. 10-17), the settlement method, and any        additional information on billing account 1061 (FIGS. 10-17),        and/or recipient account 1062 (FIGS. 10-17).

In some embodiments, the debit call can be sent to sending participant1040 (FIGS. 10-17), and given successful execution of the debit call,sending account 1041 (FIGS. 10-17) can be decremented. In someembodiments, the structure of the debit call can leverage the sameInquiry framework that has already been developed and used for DepositChek® Direct, offered by Early Warning Services, LLC.

In several embodiments, the debit call can include various elements inthe inquiry messages (e.g., messages 1173 (FIG. 11), 1272 (FIG. 12),1472 (FIG. 14), 1673 (FIG. 16), and/or 1773 (FIG. 17)). The transactionsystem can get this inquiry if the transaction system is in datacommunication with the sending recipient. Otherwise the “billingintermediary” handles this debiting. After the “debiting Inquiry” hashappened, the debiting response can be received by either thetransaction system or the billing intermediary. In some embodiments,various elements in the inquiry of the debit call (e.g., messages 1773(FIG. 11), 1272 (FIG. 12), 1472 (FIG. 14), 1673 (FIG. 16), and/or 1773(FIG. 17)) can include:

-   -   a. Message wrapper fields: This section of the inquiry message        can include fields, such as transaction ID, transaction date,        etc.    -   b. Debit block: This section of the inquiry message can provide        information on sender account 1041 (FIGS. 10-17). Data elements        can include ABA, account number, etc.    -   c. Settlement block: This section of the inquiry message can        provide settlement fields from receiving participant 1060 (FIGS.        10-17), which were returned in the “is account real-time capable        call” response message. Data elements can include information        for receiving participant settlement account 1063 (FIGS. 10-17),        the settlement method, and any additional information on billing        account 1061 (FIGS. 10-17), and/or recipient account 1062 (FIGS.        10-17).

In several embodiments, the debit call can include various elements inthe response messages (e.g., messages 1174 (FIG. 11), 1273 (FIG. 12),1473 (FIG. 14), 1674 (FIG. 16), and/or 1774 (FIG. 17)). The debitresponse can come from the sending participant 1040 (FIGS. 10-17) inresponse to the payment debit inquiry. If transaction system 1050 (FIGS.10-17) receives this response then it can be forwarded to theapplication service provider (e.g., 1030 (FIGS. 10-12), 1330 (FIGS.13-14), and/or 1530 (FIGS. 15-17). However, in some embodiments, if theapplication service provider (e.g., 1030 (FIGS. 10-12), 1330 (FIGS.13-14), and/or 1530 (FIGS. 15-17) receives this response, it is notforwarded to transaction system 1050 (FIGS. 10-17). In otherembodiments, the response can be forwarded to transaction system 1050(FIGS. 10-17). In some embodiments, various elements in the response(e.g., messages 1174 (FIG. 11), 1273 (FIG. 12), 1473 (FIG. 14), 1674(FIG. 16), and/or 1774 (FIG. 17)) of the debit call can include:

-   -   a. Message wrapper fields: This section of the response message        can fields, such as transaction ID, transaction date, etc.    -   b. Debit block: This section of the response message can return        fields from sending participant 1040 (FIGS. 10-17), which        maintains sender account 1041 (FIGS. 10-17) for sender 1010        (FIGS. 10-17). Data elements can include: a payment guarantee        flag, a payment guarantee expiration date, and reason codes if        the payment guarantee is not offered.

In some embodiments, the credit call, also known as the promise-to-pay,can be sent to receiving participant 1060 (FIGS. 10-17), after the debitcall has been successfully executed and payment guarantee was offered.In some embodiments, the structure of the credit call can leverage thesame Inquiry framework that has already been developed and used forDeposit Chek® Direct, offered by Early Warning Services, LLC. In anumber of embodiments, the process can be handled through transactionsystem 1050 (FIGS. 10-17). If transaction system 1050 (FIG. 1017) doesthe debit call then can forward the debit call to the applicationservice provider (e.g., 1030 (FIGS. 10-12), 1330 (FIGS. 13-14), and/or1530 (FIGS. 15-17), and then the application service provider (e.g.,1030 (FIGS. 10-12), 1330 (FIGS. 13-14), and/or 1530 (FIGS. 15-17) cansend the credit call to transaction system 1050 (FIGS. 10-17).

In several embodiments, the credit call can include various elements inthe inquiry messages (e.g., messages 1176-1177 (FIG. 11), 1274-1275(FIG. 12), 1474-1475 (FIG. 14), 1676-1677 (FIG. 16), and/or 1776 (FIG.17)). In some embodiments, the credit call inquiry can be sent throughtransaction system 1050 (FIGS. 10-17). The various elements of theinquiry of the credit call (e.g., messages 1176-1177 (FIG. 11),1274-1275 (FIG. 12), 1474-1475 (FIG. 14), 1676-1677 (FIG. 16), and/or1776 (FIG. 17) can include:

-   -   a. Message wrapper fields: This section of the response message        can fields, such as transaction ID, transaction date, etc.    -   b. Payment item block: This section of the inquiry message can        provide information on the item (e.g., a credit card payment)        for which the consumer wishes to make a payment. Data elements        can include billing account information, customer PII, etc.

In several embodiments, the credit call can include various elements inthe response messages (e.g., messages 1178-1180 (FIG. 11), 1276-1278(FIG. 12), 1476-1478 (FIG. 14), 1678-1680 (FIG. 16), and/or 1777-1778(FIG. 17)), such as:

-   -   a. Message wrapper fields: This section of the response message        can fields, such as transaction ID, transaction date, etc.    -   b. Payment item block: This section of the response message can        return fields from the receiving participant 1060 (FIGS. 10-17),        which in some instances can be the biller. Data elements can        include a payment credit success flag, reason codes if credit is        not successful, customer message fields, customer support phone        numbers, and other optional fields on billing account 1061        (FIGS. 10-17) for the customer (e.g., sender 1010 (FIGS.        10-17)).

In some embodiments, logging and monitoring can be provided intransaction system 1050 (FIGS. 10-17). In a number of embodiments,incoming and outgoing message data can be logged so that the informationcan be available for billing, statistical and reporting, and/or clientlogs, if applicable. In some embodiments, transaction system 1050 (FIGS.10-17) can include logging, which can advantageously provide at one ormore of the following advantages, among other benefits:

-   -   a. Log message data at a switch of transaction system 1050        (FIGS. 10-17) can be made available for research, corporate,        and/or client reporting purposes.    -   b. Message validation or communication failures between        transaction system 1050 (FIGS. 10-17) on one hand, and receiving        sending participant 1040 (FIGS. 10-17) and/or receiving        participant 1060 (FIGS. 10-17) on the other hand, can be logged        to new logs so they are made available for alerting.    -   c. Failures can be logged at transaction system 1050 (FIGS.        10-17) for messages, which can allow alerts to be triggered        based on severity. Logged data can be used for research        purposes.    -   d. Logging can allow transaction system 1050 (FIGS. 10-17) to        reconcile messages for billing (such as reversals and other        types of transactions).    -   e. System monitoring of transactions for various issues such as        excessive timeouts, invalid message formats, etc. can be        provided, and alerts can be provided in real-time.

In a number of embodiments, the financial institutions, such as sendingrecipient 1040 (FIGS. 10-17) and/or receiving recipient 1060 (FIGS.10-17), can include logging, which can provide pertinent detail onsummary of counts and response times at transaction system 1050 (FIGS.10-17).

In a number of embodiments, connectivity can exist between participants,such as participating financial institutions (sending recipient 1040(FIGS. 10-17) and/or receiving recipient 1060 (FIGS. 10-17)), andapplication service providers, (e.g., application service provider 1030(FIGS. 10-12)). Dedicated circuits can be implemented to establish newconnections or to supplement if existing pipe capacity of transactionsystem 1050 (FIGS. 10—is already maxed out.

In a number of embodiments, transaction system 1050 (FIGS. 10-17) canassess if connectivity with capacity already exists or new pipes need tobe established to support connectivity needs. New participants, such asa new one of application service provider 1030 (FIGS. 10-12), can beprovided new connectivity. In some embodiments, one or more of thefollowing capabilities, among others, can be facilitated via thededicated circuits:

-   -   a. Real-time messaging capability between participants        supporting the following message types:        -   i. Account real-time capable call        -   ii. Debit call        -   iii. Credit call        -   iv. Reversal call    -   b. FTP connections established for reporting and activity        payment file transfer.    -   c. Web service connections for reporting and dashboard sharing.

In many embodiments, transaction system 1050 (FIGS. 10-17) can host andmaintain a biller directory for message routing purposes. This directorycan be complimentary to a biller directory of application serviceprovider 1030 (FIGS. 10-12). This directory can link billers tofinancial institutions (1040 (FIGS. 10-17) and/or receiving recipient1060 (FIGS. 10-17)), and can be updated with the “is account real-timecapable call” response information.

In some of to the settlement types described above, or in addition tothe settlement types described above, in various embodiments, settlementcan occur between sending participant 1040 (FIGS. 10-17) and receivingparticipant 1060 (FIGS. 10-17) using conventional methods (e.g.,existing rails) to move the money from sending participant 1040 (FIGS.10-17) to receiving participant (FIGS. 10-17). In many embodiments,transaction system 1050 (FIGS. 10-17) can send batch files to thefinancial institutions (e.g., the sending participant 1040 (FIGS. 10-17)and/or the receiving participant 1060 (FIGS. 10-17)) with reconciliationinformation.

In a number of embodiments, application service provider 1030 (FIGS.10-12) can serve as a third party settlement agent and sendreconciliation files, and settlement can be handled by applicationservice provider 1030 (FIGS. 10-12). In some embodiments, reconciliationinformation can be sent from application service provider 1030 (FIGS.10-12) to sending participant 1040 (FIGS. 10-17) and/or receivingparticipant 1060 (FIGS. 10-17).

In various embodiments, a third party settlement agent can be differentfrom application service provider 1330 (FIGS. 13-14) when applicationservice provider is the same entity as sending participant 1040 (FIGS.10-17). The third party settlement agent can settle the transactionwithout being involved in the payment messages.

In various embodiments, settlement can be handled by transaction system1050 (FIGS. 10-17). In some embodiments, transaction system 1050 (FIGS.10-17) can include a payment/settlement system, which can providemovement of funds between financial institutions (e.g., sendingparticipant 1040 (FIGS. 10-17) and/or receiving participant 1060 (FIGS.10-17)), the ability to view transactions, the ability to reconciletransactions, the posting of files to the Federal Reserve, and networkfee settlement, among other benefits.

In many embodiments, in the response of the “is account real-timecapable call,” receiving participant 1060 (FIGS. 10-17) and/or therecipient/biller can indicate the manner in which they prefer to settlethe transaction, which can be their most desired settlement method. Forexample, it could be through a card network, through the ACH system, orit could be through a payment/settlement system of transaction system1050 (FIGS. 10-17). This settlement method can be included in theresponse message (e.g., messages 1074, 1076-1078 (FIG. 10), 1374-1376(FIG. 13), and/or messages 1574-1576 (FIG. 15)).

In a number of embodiments, receiving participant 1060 (FIGS. 10-17) canselect whether it prefers clearing and settlement for each individualitem or in groups. Once the debit call process occurs, funds can betaken out of sender account 1041 (FIGS. 10-17) to pay the bill. Thesefunds are then moved for the credit push notification. In someembodiments, the funds can be made available within a few seconds. Theactual transfer of funds between the financial institutions can occurthrough the day, multiple times a day, such as every minute, every 5seconds, every 3 seconds, every second, and/or for every transaction.This can occur within a few seconds up to multiple times throughout theday. Unlike conventional methods and system, in which transactions aredone in batch and net settled, transaction can be individually settled.In some embodiments, the payment/settlement system of transaction system1050 (FIGS. 10-17) can allow for single transactions to be settled inreal-time. In other embodiments, debit networks or other suitablesettlement rails can be used. There can be settlement instructionsprovided by the biller and/or receiving participant 1060 (FIGS. 10-17),indicating how they prefer the transaction to be settled.

In some embodiments, transaction system 1050 (FIGS. 10-17) can allow fora sending participant 1040 (FIGS. 10-17) or receiving participant 1060(FIGS. 10-17) to receive a debit call success for a promise-to-pay, senda promise-to-pay, and/or transfer funds (e.g., settle funds) to or froma financial institution that is not a participant (e.g., not a sendingparticipant 1040 (FIGS. 10-17) or receiving participant 1060 (FIGS.10-17)). For example, transaction system 1050 (FIGS. 10-17) can convertmessages to one or more other protocols for real-time funds transfer orreal-time promise-to-pay, such as Visa Original Credit Transaction (OCT)transactions to push funds to a non-participating financial institution,or a Visa Account Funding Transaction (AFT) transaction to pull fundsfrom a non-participating financial institution, or a debit transactionmessage, or other suitable protocols. In some embodiments, transactionsystem 1050 (FIGS. 10-17) can include a directory for non-participatingfinancial institutions, which can provide transaction system 1050 (FIGS.10-17) with information on how to connect to the non-participatingfinancial institution. In a number of embodiments, transaction system1050 (FIGS. 10-17) can allow for international payment in a similarmanner, such as by using a suitable protocol, such as the SWIFT (Societyfor Worldwide Interbank Financial Telecommunication) wire network, Visa,MasterCard, PayPal, Alibaba Secure Payment, etc.

Turning ahead in the drawings, FIG. 18 illustrates a flow chart for amethod 1800 to facilitate a real-time funds availability bill-paytransaction, according to an embodiment. Method 1800 is merely exemplaryand is not limited to the embodiments presented herein. Method 1800 canbe employed in many different embodiments or examples not specificallydepicted or described herein. In some embodiments, the procedures, theprocesses, and/or the activities of method 1800 can be performed in theorder presented. In other embodiments, the procedures, the processes,and/or the activities of method 1800 can be performed in any suitableorder. In still other embodiments, one or more of the procedures, theprocesses, and/or the activities of method 1800 can be combined orskipped. In some embodiments, method 1800 can be performed bytransaction system 1050 (FIGS. 10-17).

Referring to FIG. 18, method 1800 can include a block 1801 of optionalfirst steps, as shown in FIG. 19 and described below. In someembodiments, method 1800 can skip block 1801 of optional first steps.

In a number of embodiments, method 1800 also can include a block 1802 ofoptional second steps, as shown in FIG. 20 and described below. In someembodiments, method 1800 can skip block 1802 of optional second steps.

In several embodiments, method 1800 additionally can include a block1803 of receiving a first promise-to-pay message at a transactionsystem. The first promise-to-pay message can be similar or identical tomessages 1176 (FIG. 11), 1274 (FIG. 12), 1474 (FIG. 14), and/or 1676(FIG. 16). The transaction system can be similar or identical totransaction system 1050 (FIGS. 10-17). In some embodiments, the firstpromise-to-pay message can be based on a successful debit of a firstaccount maintained by a first financial institution. The first financialinstitution can be similar or identical to sending participant 1040(FIGS. 10-17). The first account can be similar or identical to senderaccount 1041 (FIGS. 10-17). The successful debit can be similar oridentical to activity 1145 (FIGS. 11-12, 14, 16-17). In manyembodiments, the successful debit of the first account can be based on apayment authorization made by a sender at a payment authorization time.The payment authorization can be to authorize the payment of one or morebills and/or other financial obligations. The payment authorization timecan be the time in which the sender authorized the bill paymenttransaction. The sender can be similar or identical to sender 1010(FIGS. 10-17), who can use sender system 1020 (FIGS. 10-17). The paymentauthorization can be communicated from sender system 1020 (FIGS. 10-17)in messages 1171 (FIG. 11), 1271 (FIG. 12), 1471 (FIG. 14), and/or 1671(FIG. 16). In several embodiments, the first account can be held by thesender, such that the sender is the account holder of the first account.

In some embodiments, the first promise-to-pay message can be sent to thetransaction system from an application service provider. The applicationservice provider can be similar or identical to application serviceprovider 1030 (FIGS. 10-12), application service provider 1330 (FIGS.13-14), and/or application service provider 1530 (FIGS. 15-17). In manyembodiments, the application service provider can host a paymentapplication that can be accessed by the sender to perform the paymentauthorization. The payment application can be similar or identical topayment application 1031 (FIGS. 10-12), payment application 1331 (FIGS.13-14), and/or payment application 1531 (FIGS. 15-17).

In a number of embodiments, method 1800 further can include a block 1804of storing the first promise-to-pay message in the transaction system.

In several embodiments, method 1800 additionally can include a block1805 of sending a second promise-to-pay message from the transactionsystem to a second financial institution. The second promise-to-paymessage can be similar or identical to messages 1177 (FIG. 11), 1275(FIG. 12), 1475 (FIG. 14), and/or 1677 (FIG. 16). The second financialinstitution can be similar or identical to receiving participant 1060(FIGS. 10-17). In some embodiments, the second promise-to-pay messagecan be based on the first promise-to-pay message, such that the secondfinancial institution can credit a second account maintained by thesecond financial institution to make funds available in the secondaccount in real-time after the payment authorization time. The secondaccount can be similar or identical to billing account 1061 (FIGS.10-17) and/or recipient account 1062 (FIGS. 10-17). In variousembodiments, the sender can be financially liable for the secondaccount. In some embodiments, the first financial institution can bedifferent from the second financial institution.

In a number of embodiments, method 1800 further can include a block 1806of receiving a first response at the transaction system from the secondfinancial institution indicating a successful credit of the secondaccount maintained by the second financial institution. The firstresponse can be similar or identical to 1178 (FIG. 11), 1276 (FIG. 12),1476 (FIG. 14), and/or 1678 (FIG. 16). The successful credit can besimilar or identical to activity 1165 (FIGS. 11-12, 14, 16-17) and/oractivity 1167 (FIGS. 11-12, 14, 16-17).

In several embodiments, method 1800 additionally can include a block1807 of storing the first response in the transaction system.

In a number of embodiments, method 1800 further can include a block 1808of sending a second response from the transaction system indicating thesuccessful credit of the second account maintained by the secondfinancial institution to inform at least the sender in real-time afterthe payment authorization time of the successful credit of the secondaccount maintained by the second financial institution. The secondresponse can be similar or identical to messages 1179 (FIG. 11), 1277(FIG. 12), 1477 (FIG. 14), and/or 1679 (FIG. 16). The sender can beinformed by messages 1180 (FIG. 11), 1278 (FIG. 12), 1478 (FIG. 14),and/or 1680 (FIG. 16).

In some embodiments, the application service provider can be a differententity from the first and second financial institutions, such asapplication service provider 1030 (FIGS. 10-12). In other embodiments,the application service provider can be the same entity as the firstfinancial institution, such as application service provider 1330 (FIGS.13-14). In yet other embodiments, the application service provider canbe the same entity as the second financial institution, such asapplication service provider 1530 (FIGS. 15-17).

In various embodiments, the first promise-to-pay message received at thetransaction system from the application service provider can be based onthe application service provider having sent a debit message to thefirst financial institution to debit the first account maintained by thefirst financial institution and having received a debit response fromthe first financial institution in real-time after the paymentauthorization time. The debit message can be similar or identical tomessage 1272 (FIG. 12) and/or 1472 (FIG. 14). The debit response can besimilar or identical to message 1273 (FIG. 12) and/or message 1473 (FIG.14). In some embodiments, the debit response can indicate the successfuldebit of the first account maintained by the first financialinstitution.

In many embodiments, the first financial institution can maintain afirst settlement account. The first settlement account can be similar oridentical to sending participant settlement account 1042 (FIGS. 10-17).In a number of embodiments, the first settlement account can be creditedto account for the successful debit of the first account maintained bythe first financial institution, such as in activity 1146 (FIGS. 11-12,14, 16-17).

In several embodiments, the second financial institution can maintain asecond settlement account. The second settlement account can be similaror identical to receiving participant settlement account 1063 (FIGS.10-17). The second settlement account can be debited to account for thesuccessful credit of the second account maintained by the secondfinancial institution, such as in activity 1166 (FIGS. 11-12, 14,16-17).

In several embodiments, funds can be transferred from the firstsettlement account to the second settlement account in a settlementcompletion. The settlement completion can be similar or identical toactivities 1191 (FIGS. 11-12), 1192 (FIGS. 11-12), and/or 1491 (FIGS.14, 16-17). In some embodiments, the settlement completion can be partof a net settlement as a single item ACH. In other embodiments, thesettlement completion can be part of a net settlement as part of a batchACH. In yet other embodiments, the settlement completion can be part ofa net settlement as part of a wire advice file. In some embodiments, thesuccessful credit of the second account maintained by the secondfinancial institution can involve a hard credit to the second account inreal-time after the payment authorization time. In various embodiments,the settlement completion can involve the funds being transferredthrough a third settlement account of a payment processor. The thirdsettlement account can be similar or identical to payment processorsettlement account 1033 (FIGS. 10-12). In some embodiments, thesettlement completion can occur in real-time after the paymentauthorization time.

Turning ahead in the drawings, FIG. 19 illustrates a block 1801 ofoptional first steps, according to an embodiment. Block 1801 is merelyexemplary and is not limited to the embodiments presented herein. Block1801 can be employed in many different embodiments or examples notspecifically depicted or described herein. In some embodiments, theprocedures, the processes, and/or the activities of block 1801 can beperformed in the order presented. In other embodiments, the procedures,the processes, and/or the activities of block 1801 can be performed inany suitable order. In still other embodiments, one or more of theprocedures, the processes, and/or the activities of block 1801 can becombined or skipped. In many embodiments, block 1801 can be performedbefore the payment authorization time.

Referring to FIG. 19, block 1801 can include a block 1901 of receiving afirst capability inquiry at the transaction system from the applicationservice provider. The first capability inquiry can be similar oridentical to messages 1072 (FIG. 10), 1372 (FIG. 13), and/or 1572 (FIG.15).

In a number of embodiments, block 1801 also can include a block 1902 ofstoring the first capability inquiry in the transaction system.

In several embodiments, block 1801 optionally can include a block 1903of sending a second capability inquiry from the transaction system tothe second financial institution to determine whether the second accountmaintained by the second financial institution supports real-timepayment transactions. The second capability inquiry can be similar oridentical to messages 1073 (FIG. 10) and/or 1373 (FIG. 13).

In a number of embodiments, block 1801 also can include, after block1903, a block 1904 of receiving a first capability response at thetransaction system from the second financial institution indicatingwhether the second account maintained by the second financialinstitution supports real-time payment transactions. The firstcapability response can be similar or identical to messages 1074 (FIG.10) and/or 1374 (FIG. 13).

In several embodiments, block 1801 additionally can include, after block1904, a block 1905 of storing the first capability response in thetransaction system.

In a number of embodiments, block 1801 optionally can include, afterblock 1902 or block 1905, a block 1906 of sending a third capabilityinquiry from the transaction system to the first financial institutionto determine whether the first account maintained by the first financialinstitution supports real-time payment transactions. The thirdcapability inquiry can be similar or identical to messages 1075 (FIG.10) and/or 1573 (FIG. 15).

In several embodiments, block 1801 also can include, after block 1906, ablock 1907 of receiving a second capability response at the transactionsystem from the first financial institution indicating whether the firstaccount maintained by the first financial institution supports real-timepayment transactions. The second capability response can be similar oridentical to messages 1076 (FIG. 10) and/or 1574 (FIG. 15).

In a number of embodiments, block 1801 further can include, after block1907, a block 1908 of storing the second capability response in thetransaction system.

In several embodiments, block 1801 additionally can include, after block1905 or block 1908, a block 1909 of sending a third capability responsefrom the transaction system to the application service provider. In someembodiments, the third capability response can indicate whether thefirst and second accounts support real-time payment transactions, suchas in message 1077 (FIG. 11). In other embodiments, the third capabilityresponse can indicate whether the second account supports real-timepayment transactions, such as in message 1375 (FIG. 13). In yet otherembodiments, the third capability response can indicate whether thefirst account supports real-time payment transactions, such as inmessage 1575 (FIG. 15).

Turning ahead in the drawings, FIG. 20 illustrates a block 1802 ofoptional second steps, according to an embodiment. Block 1802 is merelyexemplary and is not limited to the embodiments presented herein. Block1802 can be employed in many different embodiments or examples notspecifically depicted or described herein. In some embodiments, theprocedures, the processes, and/or the activities of block 1802 can beperformed in the order presented. In other embodiments, the procedures,the processes, and/or the activities of block 1802 can be performed inany suitable order. In still other embodiments, one or more of theprocedures, the processes, and/or the activities of block 1802 can becombined or skipped. In many embodiments, block 1802 can occur beforethe payment authorization time. In many embodiments, block 1802 can beperformed before receiving the first promise-to-pay message in block1803 (FIG. 18).

Referring to FIG. 20, block 1802 can include a block 2001 of sending adebit message from the transaction system to the first financialinstitution to debit the first account maintained by the first financialinstitution. The debit message can be similar or identical to messages1173 (FIG. 11) and/or 1673 (FIG. 16).

In a number of embodiments, block 1802 also can include a block 2002 ofreceiving a debit response at the transaction system from the firstfinancial institution in real-time after the payment authorization time.The debit response can be similar or identical to messages 1174 (FIG.11) and/or 1674 (FIG. 16). In some embodiments, the debit response canindicate the successful debit of the first account maintained by thefirst financial institution.

In several embodiments, block 1802 additionally can include a block 2003of storing the debit response in the transaction system.

In a number of embodiments, block 1802 further can include a block 2004of sending a third response from the transaction system to theapplication service provider indicating the successful debit of thefirst account maintained by the first financial institution. The thirdresponse can be similar or identical to messages 1175 (FIG. 11) and/orFIG. 1675 (FIG. 16).

Proceeding to the next drawing, FIG. 21 illustrates a flow chart for amethod 2100 to facilitate a real-time funds availability bill-paytransaction, according to an embodiment. Method 2100 is merely exemplaryand is not limited to the embodiments presented herein. Method 2100 canbe employed in many different embodiments or examples not specificallydepicted or described herein. In some embodiments, the procedures, theprocesses, and/or the activities of method 2100 can be performed in theorder presented. In other embodiments, the procedures, the processes,and/or the activities of method 2100 can be performed in any suitableorder. In still other embodiments, one or more of the procedures, theprocesses, and/or the activities of method 2100 can be combined orskipped. In some embodiments, method 2100 can be performed bytransaction system 1050 (FIGS. 10-17).

Referring to FIG. 21, method 2100 can include a block 2101 of sending adebit message from a transaction system to a first financial institutionto debit a first account maintained by the first financial institutionbased on a payment authorization made by a sender at a paymentauthorization time. The debit message can be similar or identical tomessage 1773 (FIG. 17). The transaction system can be similar oridentical to transaction system 1050 (FIGS. 10-17). The first financialinstitution can be similar or identical to sending participant 1040(FIGS. 10-17). The first account can be similar or identical to senderaccount 1041 (FIGS. 10-17). The payment authorization time can be thetime in which the sender authorized the bill payment transaction. Thesender can be similar or identical to sender 1010 (FIGS. 10-17), who canuse sender system 1020 (FIGS. 10-17). The payment authorization can becommunicated from sender system 1020 (FIGS. 10-17) in message 1771 (FIG.17). In many embodiments, the first account can be held by the sender,such that the sender is the account holder of the first account.

In a number of embodiments, method 2100 also can include a block 2102 ofreceiving a debit response at the transaction system from the firstfinancial institution in real-time after the payment authorization time.The debit response can be similar or identical to debit response 1774(FIG. 17). In some embodiments, the debit response can indicate asuccessful debit of the first account maintained by the first financialinstitution. The successful debit can be similar or identical toactivity 1145 (FIGS. 11-12, 14, 16-17).

In several embodiments, method 2100 additionally can include a block2103 of storing the debit response in the transaction system.

In a number of embodiments, method 2100 further can include a block 2104of sending a first response to an application service providerindicating the successful debit of the first account maintained by thefirst financial institution, such that the application service providersends a promise-to-pay message to a second financial institution tocredit a second account maintained by the second financial institutionto make funds available in the second account in real-time after thepayment authorization time, and such that the application serviceprovider informs the sender in real-time after the payment authorizationtime of a successful credit of the second account maintained by thesecond financial institution. The first response can be similar oridentical to message 1775 (FIG. 17). The application service providercan be similar or identical to application service provider 1530 (FIGS.15-17). The successful credit can be similar or identical to activity1165 (FIGS. 11-12, 14, 16-17) and/or activity 1167 (FIGS. 11-12, 14,16-17). In many embodiments, the application service provider can be thesame entity as the second financial institution. The promise-to-paymessage can be similar or identical to message 1776 (FIG. 17). Thesecond financial institution can be similar or identical to receivingparticipant 1060 (FIGS. 10-17). The second account can be similar oridentical to billing account 1061 (FIGS. 10-17) and/or recipient account1062 (FIGS. 10-17). In various embodiments, the sender can befinancially liable for the second account. In some embodiments, thefirst financial institution can be different from the second financialinstitution.

In many embodiments, the application service provider can host a paymentapplication that is accessed by the sender to perform the paymentauthorization. The payment application can be similar or identical topayment application 1531 (FIGS. 15-17).

In many embodiments, the first financial institution can maintain afirst settlement account. The first settlement account can be similar oridentical to sending participant settlement account 1042 (FIGS. 10-17).In a number of embodiments, the first settlement account can be creditedto account for the successful debit of the first account maintained bythe first financial institution, such as in activity 1146 (FIGS. 11-12,14, 16-17).

In several embodiments, the second financial institution can maintain asecond settlement account. The second settlement account can be similaror identical to receiving participant settlement account 1063 (FIGS.10-17). The second settlement account can be debited to account for thesuccessful credit of the second account maintained by the secondfinancial institution, such as in activity 1166 (FIGS. 11-12, 14,16-17).

In several embodiments, funds can be transferred from the firstsettlement account to the second settlement account in a settlementcompletion. The settlement completion can be similar or identical toactivities 1191 (FIGS. 11-12), 1192 (FIGS. 11-12), and/or 1491 (FIGS.14, 16-17). In some embodiments, the settlement completion can be partof a net settlement as a single item ACH. In other embodiments, thesettlement completion can be part of a net settlement as part of a batchACH. In yet other embodiments, the settlement completion can be part ofa net settlement as part of a wire advice file. In some embodiments, thesuccessful credit of the second account maintained by the secondfinancial institution can involve a hard credit to the second account inreal-time after the payment authorization time. In some embodiments, thesettlement completion can occur in real-time after the paymentauthorization time.

Turning ahead in the drawings, FIG. 22 illustrates a flow chart for amethod 2200 to facilitate a real-time funds availability bill-paytransaction, according to an embodiment. Method 2200 is merely exemplaryand is not limited to the embodiments presented herein. Method 2200 canbe employed in many different embodiments or examples not specificallydepicted or described herein. In some embodiments, the procedures, theprocesses, and/or the activities of method 2200 can be performed in theorder presented. In other embodiments, the procedures, the processes,and/or the activities of method 2200 can be performed in any suitableorder. In still other embodiments, one or more of the procedures, theprocesses, and/or the activities of method 2200 can be combined orskipped. In some embodiments, method 2200 can be performed by firstfinancial institution 1040 (FIGS. 10-17).

Referring to FIG. 22, method 2200 can include a block 2201 of optionalfirst steps, as shown in FIG. 23 and described below. In someembodiments, method 2200 can skip block 2201 of optional first steps.

In a number of embodiments, method 2200 also can include a block 2202 ofreceiving a debit message at a first financial institution to debit afirst account maintained by the first financial institution based on apayment authorization for a payment amount made by a sender at a paymentauthorization time. The debit message can be similar or identical tomessages 1173 (FIG. 11), 1272 (FIG. 12), 1472 (FIG. 14), 1673 (FIG. 16),and/or 1773 (FIG. 17). The first financial institution can be similar oridentical to sending participant 1040 (FIGS. 10-17). The first accountcan be similar or identical to sender account 1041 (FIGS. 10-17). Thepayment authorization time can be the time in which the senderauthorized the bill payment transaction. The sender can be similar oridentical to sender 1010 (FIGS. 10-17), who can use sender system 1020(FIGS. 10-17). The payment authorization can be communicated from sendersystem 1020 (FIGS. 10-17) in messages 1171 (FIG. 11), 1271 (FIG. 12),1471 (FIG. 14), 1671 (FIG. 16), and/or 1771 (FIG. 17). In severalembodiments, the first account can be held by the sender, such that thesender is the account holder of the first account.

In several embodiments, method 2200 additionally can include a block2203 of performing a successful debit for the payment amount from thefirst account maintained by the first financial institution in real-timeafter the payment authorization time. The successful debit can besimilar or identical to activity 1145 (FIGS. 11-12, 14, 16-17).

In a number of embodiments, method 2200 optionally can include a block2204 of performing a credit for the payment amount to a first settlementaccount maintained by the first financial institution to account for thesuccessful debit of the first account maintained by the first financialinstitution. The first settlement account can be similar or identical tosending participant settlement account 1042 (FIGS. 10-17). The creditcan be similar or identical to activity 1146 (FIGS. 11-12, 14, 16-17).

In a several embodiments, method 2200 further can include, after block2203 or block 2204, a block 2205 of sending a debit response from thefirst financial institution in real-time after the payment authorizationtime. The debit response can be similar or identical to messages 1174(FIG. 11), 1273 (FIG. 12), 1473 (FIG. 14), 1674 (FIG. 16), and/or 1774(FIG. 17). In many embodiments, the debit response can indicate thesuccessful debit of the first account maintained by the first financialinstitution, such that an application service provider sends a firstpromise-to-pay message for a second financial institution to credit asecond account maintained by the second financial institution to makefunds available in the second account in real-time after the paymentauthorization time, and such that the application service providerinforms the sender in real-time after the payment authorization time ofa successful credit of the second account maintained by the secondfinancial institution.

The application service provider can be similar or identical toapplication service provider 1030 (FIGS. 10-12), application serviceprovider 1330 (FIGS. 13-14), and/or application service provider 1530(FIGS. 15-17). The first promise-to-pay messages can be similar oridentical to messages 1176 (FIG. 11), 1274 (FIG. 12), 1474 (FIG. 14),1676 (FIG. 16), and/or 1776 (FIG. 17). The second financial institutioncan be similar or identical to receiving participant 1060 (FIGS. 10-17).The second account can be similar or identical to billing account 1061(FIGS. 10-17) and/or recipient account 1062 (FIGS. 10-17). Thesuccessful credit can be similar or identical to activity 1165 (FIGS.11-12, 14, 16-17) and/or activity 1167 (FIGS. 11-12, 14, 16-17). Thesender can be informed by messages 1180 (FIG. 11), 1278 (FIG. 12), 1478(FIG. 14), 1680 (FIG. 16), and/or 1778 (FIG. 17). In variousembodiments, the sender can be financially liable for the secondaccount. In some embodiments, the first financial institution can bedifferent from the second financial institution.

In some embodiments, the first promise-to-pay message can be sent to atransaction system from the application service provider. Thetransaction system can be similar or identical to transaction system1050 (FIGS. 10-17). In many embodiments, the transaction system can senda second promise-to-pay message to the second financial institutionbased on the first promise-to-pay message. The second promise-to-paymessage can be similar or identical to messages 1176 (FIG. 11), 1274(FIG. 12), 1474 (FIG. 14), and/or 1676 (FIG. 16).

In other embodiments, the first promise-to-pay message can be sent fromthe application service provider to the second financial institutionafter the application service provider receives a second debit responseindicating the successful debit of the first account maintained by thefirst financial institution. The second debit response can be similar oridentical to message 1775 (FIG. 17).

In many embodiments, the application service provider can host a paymentapplication that can be accessed by the sender to perform the paymentauthorization. The payment application can be similar or identical topayment application 1031 (FIGS. 10-12), payment application 1331 (FIGS.13-14), and/or payment application 1531 (FIGS. 15-17).

In some embodiments, the application service provider can be a differententity from the first and second financial institutions, such asapplication service provider 1030 (FIGS. 10-12). In other embodiments,the application service provider can be the same entity as the firstfinancial institution, such as application service provider 1330 (FIGS.13-14). In yet other embodiments, the application service provider canbe the same entity as the second financial institution, such asapplication service provider 1530 (FIGS. 15-17).

In some embodiments, the debit message can be received from thetransaction system, such as in messages 1173 (FIG. 11), 1673 (FIG. 16),and/or 1773 (FIG. 17), and the debit response can be sent to thetransaction system, such as in messages 1174 (FIG. 11), 1674 (FIG. 16),and/or 1774 (FIG. 17). In other embodiments, the debit message can bereceived from the application service provider, such as in messages 1272(FIG. 12) and/or 1472 (FIG. 14), and the debit response can be sent tothe transaction system, such as in messages 1273 (FIG. 12) and/or 1473(FIG. 14).

In many embodiments, the first financial institution can maintain afirst settlement account. The first settlement account can be similar oridentical to sending participant settlement account 1042 (FIGS. 10-17).In a number of embodiments, the first settlement account can be creditedto account for the successful debit of the first account maintained bythe first financial institution, such as in activity 1146 (FIGS. 11-12,14, 16-17).

In several embodiments, the second financial institution can maintain asecond settlement account. The second settlement account can be similaror identical to receiving participant settlement account 1063 (FIGS.10-17). The second settlement account can be debited to account for thesuccessful credit of the second account maintained by the secondfinancial institution, such as in activity 1166 (FIGS. 11-12, 14,16-17).

In many embodiments, funds can be transferred from the first settlementaccount to the second settlement account in a settlement completion. Thesettlement completion can be similar or identical to activities 1191(FIGS. 11-12), 1192 (FIGS. 11-12), and/or 1491 (FIGS. 14, 16-17). Insome embodiments, the settlement completion can be part of a netsettlement as a single item ACH. In other embodiments, the settlementcompletion can be part of a net settlement as part of a batch ACH. Inyet other embodiments, the settlement completion can be part of a netsettlement as part of a wire advice file. In some embodiments, thesuccessful credit of the second account maintained by the secondfinancial institution can involve a hard credit to the second account inreal-time after the payment authorization time. In various embodiments,the settlement completion can involve the funds being transferredthrough a third settlement account of a payment processor. The thirdsettlement account can be similar or identical to payment processorsettlement account 1033 (FIGS. 10-12). In some embodiments, thesettlement completion can occur in real-time after the paymentauthorization time.

Proceeding to the next drawing, FIG. 23 illustrates a block 2201 ofoptional first steps, according to an embodiment. Block 2201 is merelyexemplary and is not limited to the embodiments presented herein. Block2201 can be employed in many different embodiments or examples notspecifically depicted or described herein. In some embodiments, theprocedures, the processes, and/or the activities of block 2201 can beperformed in the order presented. In other embodiments, the procedures,the processes, and/or the activities of block 2201 can be performed inany suitable order. In still other embodiments, one or more of theprocedures, the processes, and/or the activities of block 2201 can becombined or skipped. In many embodiments, block 2201 can be performedbefore the payment authorization time.

Referring to FIG. 23, block 2201 can include a block 2301 of receiving afirst capability inquiry at receiving a first capability inquiry at thefirst financial institution from the transaction system to determinewhether the first account maintained by the first financial institutionsupports real-time payment transactions. The first capability inquirycan be similar or identical to messages 1075 (FIG. 10) and/or 1573 (FIG.15).

In a number of embodiments, block 2201 also can include a block 2302 ofsending a first capability response from the first financial institutionto the transaction system indicating whether the first accountmaintained by the first financial institution supports real-time paymenttransactions, such that the transaction system sends a second capabilityresponse to the application service provider indicating whether thefirst account supports real-time payment transactions. The firstcapability response can be similar or identical to messages 1076 (FIG.10) and/or 1574 (FIG. 15). The second capability response can be similaror identical to messages 1077 (FIG. 10) and/or 1575 (FIG. 15).

Turning ahead in the drawings, FIG. 24 illustrates a flow chart for amethod 2400 to facilitate a real-time funds availability bill-paytransaction, according to an embodiment. Method 2400 is merely exemplaryand is not limited to the embodiments presented herein. Method 2400 canbe employed in many different embodiments or examples not specificallydepicted or described herein. In some embodiments, the procedures, theprocesses, and/or the activities of method 2400 can be performed in theorder presented. In other embodiments, the procedures, the processes,and/or the activities of method 2400 can be performed in any suitableorder. In still other embodiments, one or more of the procedures, theprocesses, and/or the activities of method 2400 can be combined orskipped. In some embodiments, method 2400 can be performed byapplication service provider 1030 (FIGS. 10-12), application serviceprovider 1330 (FIGS. 13-14), and/or application service provider 1530(FIGS. 15-17).

Referring to FIG. 24, method 2400 can include a block 2401 of optionalfirst steps, as shown in FIG. 25 and described below. In someembodiments, method 2400 can skip block 2401 of optional first steps.

In a number of embodiments, method 2400 also can include a block 2402 ofproviding a payment application to a sender from an application serviceprovider. The payment application can be similar or identical to paymentapplication 1031 (FIGS. 10-12), payment application 1331 (FIGS. 13-14),and/or payment application 1531 (FIGS. 15-17). The sender can be similaror identical to sender 1010 (FIGS. 10-17), who can use sender system1020 (FIGS. 10-17).

In several embodiments, method 2400 additionally can include a block2403 of receiving a bill payment authorization from the sender throughthe payment application. The payment authorization can be communicatedfrom sender system 1020 (FIGS. 10-17) in messages 1171 (FIG. 11), 1271(FIG. 12), 1471 (FIG. 14), 1671 (FIG. 16), and/or 1771 (FIG. 17). Inmany embodiments, the bill payment authorization can be made by thesender at a payment authorization time. The payment authorization timecan be the time in which the sender authorized the bill paymenttransaction.

In a number of embodiments, method 2400 further can include a block 2404of sending a first debit message from the application service providerto debit a first account maintained by a first financial institutionbased on the bill payment authorization. The first debit message can besimilar or identical to messages 1172 (FIG. 11), 1272 (FIG. 12), 1472(FIG. 14), 1672 (FIG. 16), and/or 1772 (FIG. 17). The first account canbe similar or identical to sender account 1041 (FIGS. 10-17). The firstfinancial institution can be similar or identical to sending participant1040 (FIGS. 10-17). In many embodiments, the first account can be heldby the sender, such that the sender is the account holder of the firstaccount.

In a several embodiments, method 2400 further can include a block 2405of receiving a first debit response at the application service providerin real-time after the payment authorization time. The first debitresponse can be similar or identical to messages 1175 (FIG. 11), 1273(FIG. 12), 1473 (FIG. 14), 1675 (FIG. 16), and/or 1775 (FIG. 17). Inmany embodiments, the debit response can indicate a successful debit ofthe first account maintained by the first financial institution. Thesuccessful debit can be similar or identical to activity 1145 (FIGS.11-12, 14, 16-17).

In a number of embodiments, method 2400 further can include a block 2406of generating a first promise-to-pay message for a second financialinstitution to credit a second account maintained by the secondfinancial institution to make funds available in the second account inreal-time after the payment authorization time. The first promise-to-paymessage can be similar or identical to messages 1176 (FIG. 11), 1274(FIG. 12), 1474 (FIG. 14), 1676 (FIG. 16), and/or 1776 (FIG. 17). Thesecond financial institution can be similar or identical to receivingparticipant 1060 (FIGS. 10-17). The second account can be similar oridentical to billing account 1061 (FIGS. 10-17) and/or recipient account1062 (FIGS. 10-17). In various embodiments, the sender can befinancially liable for the second account. In many embodiments, thefirst promise-to-pay message can be based on the successful debit of thefirst account maintained by the first financial institution. In manyembodiments, the first financial institution can be different from thesecond financial institution.

In a several embodiments, method 2400 further can include a block 2407of sending the first promise-to-pay message. In some embodiments, thefirst promise-to-pay message can be sent from the application serviceprovider to a transaction system, such as in messages 1176 (FIG. 11),1274 (FIG. 12), 1474 (FIG. 14), and/or 1676 (FIG. 16). In manyembodiments, a second promise-to-pay message can be sent by thetransaction system to the second financial institution based on thefirst promise-to-pay message. The second promise-to-pay message can besimilar or identical to 1177 (FIG. 11), 1275 (FIG. 12), 1475 (FIG. 14),and/or 1677 (FIG. 16). In other embodiments, the first promise-to-paymessage can be sent from the application service provider to the secondfinancial institution, such as in message 1776 (FIG. 17).

In a number of embodiments, method 2400 further can include a block 2408of receiving a first response at the application service providerindicating a successful credit of the second account maintained by thesecond financial institution. The first response can be similar oridentical to messages 1179 (FIG. 11), 1277 (FIG. 12), 1477 (FIG. 14),1679 (FIG. 16), and/or 1777 (FIG. 17). The successful credit can besimilar or identical to activity 1165 (FIGS. 11-12, 14, 16-17) and/oractivity 1167 (FIGS. 11-12, 14, 16-17).

In some embodiments, the first response, such a messages 1179 (FIG. 11),1277 (FIG. 12), 1477 (FIG. 14), 1679 (FIG. 16), can be received at theapplication service provider from the transaction system based on asecond response that was received at the transaction system from thesecond financial institution indicating the successful credit of thesecond account maintained by the second financial institution. Thesecond response can be similar or identical to messages 1177 (FIG. 11),1276 (FIG. 12), 1476 (FIG. 14), and/or 1678 (FIG. 16). In otherembodiments, the first response can be received at the applicationservice provider from the second financial institution, such as inmessage 1777 (FIG. 17).

In a several embodiments, method 2400 further can include a block 2409of sending a notification to the sender from the application serviceprovider in real-time after the payment authorization time of thesuccessful credit of the second account maintained by the secondfinancial institution. The notification can be similar or identical tomessages 1180 (FIG. 11), 1278 (FIG. 12), 1478 (FIG. 14), 1680 (FIG. 16),and/or 1778 (FIG. 17).

In some embodiments, the application service provider can be a differententity from the first and second financial institutions, such asapplication service provider 1030 (FIGS. 10-12). In other embodiments,the application service provider can be the same entity as the firstfinancial institution, such as application service provider 1330 (FIGS.13-14). In yet other embodiments, the application service provider canbe the same entity as the second financial institution, such asapplication service provider 1530 (FIGS. 15-17).

In some embodiments, the first debit message, such as messages 1172(FIG. 11), 1672 (FIG. 16), and/or 1772 (FIG. 17), can be sent from theapplication service provider to the transaction system to be forwardedby the transaction system to the first financial institution as a seconddebit message that is based on the first debit message. The second debitmessage can be similar or identical to messages 1173 (FIG. 11), 1673(FIG. 16), and/or 1773 (FIG. 17). The first debit response, such asmessages 1175 (FIG. 11), 1675 (FIG. 16), and/or 1775 (FIG. 17), can bereceived at the application service provider from the transaction systembased on a second debit response that was received at the transactionsystem from the first financial institution indicating the successfuldebit of the first account maintained by the first financialinstitution. The second debit response can be similar or identical tomessages 1174 (FIG. 11), 1674 (FIG. 16), and/or 1774 (FIG. 17).

In other embodiments, the first debit message, such as messages 1272(FIG. 12 and/or 1472 (FIG. 14), can be sent from the application serviceprovider to the first financial institution. The first debit response,such as messages 1273 (FIG. 12) and/or 1473 (FIG. 14) can be received atthe application service provider from the first financial institution.

In many embodiments, the first financial institution can maintain afirst settlement account. The first settlement account can be similar oridentical to sending participant settlement account 1042 (FIGS. 10-17).In a number of embodiments, the first settlement account can be creditedto account for the successful debit of the first account maintained bythe first financial institution, such as in activity 1146 (FIGS. 11-12,14, 16-17).

In several embodiments, the second financial institution can maintain asecond settlement account. The second settlement account can be similaror identical to receiving participant settlement account 1063 (FIGS.10-17). The second settlement account can be debited to account for thesuccessful credit of the second account maintained by the secondfinancial institution, such as in activity 1166 (FIGS. 11-12, 14,16-17).

In several embodiments, funds can be transferred from the firstsettlement account to the second settlement account in a settlementcompletion. The settlement completion can be similar or identical toactivities 1191 (FIGS. 11-12), 1192 (FIGS. 11-12), and/or 1491 (FIGS.14, 16-17). In some embodiments, the settlement completion can be partof a net settlement as a single item ACH. In other embodiments, thesettlement completion can be part of a net settlement as part of a batchACH. In yet other embodiments, the settlement completion can be part ofa net settlement as part of a wire advice file. In some embodiments, thesuccessful credit of the second account maintained by the secondfinancial institution can involve a hard credit to the second account inreal-time after the payment authorization time. In various embodiments,the settlement completion can involve the funds being transferredthrough a third settlement account of a payment processor. The thirdsettlement account can be similar or identical to payment processorsettlement account 1033 (FIGS. 10-12). In some embodiments, thesettlement completion can occur in real-time after the paymentauthorization time.

Proceeding to the next drawing, FIG. 25 illustrates a block 2401 ofoptional first steps, according to an embodiment. Block 2401 is merelyexemplary and is not limited to the embodiments presented herein. Block2401 can be employed in many different embodiments or examples notspecifically depicted or described herein. In some embodiments, theprocedures, the processes, and/or the activities of block 2401 can beperformed in the order presented. In other embodiments, the procedures,the processes, and/or the activities of block 2401 can be performed inany suitable order. In still other embodiments, one or more of theprocedures, the processes, and/or the activities of block 2401 can becombined or skipped. In many embodiments, block 2401 can be performedbefore the payment authorization time.

Referring to FIG. 25, block 2401 can include a block 2501 of sending afirst capability inquiry from the application service provider to thetransaction system. The first capability inquiry can be similar oridentical to messages 1072 (FIG. 10), 1372 (FIG. 13), and/or 1572 (FIG.15).

In a number of embodiments, block 2401 also can include a block 2502 ofreceiving a second capability response at the application serviceprovider from the transaction system. The second capability response canbe similar or identical to messages 1077 (FIG. 10), 1375 (FIG. 13),and/or 1575 (FIG. 15). In some embodiments, the second capabilityresponse can indicate whether the first and second accounts supportreal-time payment transactions, such as in message 1077 (FIG. 10). Inother embodiments, the second capability response can indicate whetherthe second account supports real-time payment transactions, such as inmessage 1375 (FIG. 13). In yet other embodiments, the second capabilityresponse can indicate whether the first account supports real-timepayment transactions, such as in message 1575 (FIG. 15).

Turning ahead in the drawings, FIG. 26 illustrates a flow chart for amethod 2600 to facilitate a real-time funds availability bill-paytransaction, according to an embodiment. Method 2600 is merely exemplaryand is not limited to the embodiments presented herein. Method 2600 canbe employed in many different embodiments or examples not specificallydepicted or described herein. In some embodiments, the procedures, theprocesses, and/or the activities of method 2600 can be performed in theorder presented. In other embodiments, the procedures, the processes,and/or the activities of method 2600 can be performed in any suitableorder. In still other embodiments, one or more of the procedures, theprocesses, and/or the activities of method 2600 can be combined orskipped. In some embodiments, method 2600 can be performed by secondfinancial institution 1060 (FIGS. 10-17).

Referring to FIG. 26, method 2600 can include a block 2601 of optionalfirst steps, as shown in FIG. 27 and described below. In someembodiments, method 2600 can skip block 2601 of optional first steps.

In a number of embodiments, method 2600 also can include a block 2602 ofreceiving a first promise-to-pay message at a second financialinstitution. The first promise-to-pay messages can be similar oridentical to messages 1177 (FIG. 11), 1275 (FIG. 12), 1475 (FIG. 14),1677 (FIG. 16), and/or 1776 (FIG. 17). The second financial institutioncan be similar or identical to receiving participant 1060 (FIGS. 10-17).In many embodiments, the first promise-to-pay message can be based on asuccessful debit of a first account maintained by a first financialinstitution. The successful debit can be similar or identical toactivity 1145 (FIGS. 11-12, 14, 16-17). The first financial institutioncan be similar or identical to sending participant 1040 (FIGS. 10-17).The first account can be similar or identical to sender account 1041(FIGS. 10-17). In many embodiments, the successful debit of the firstaccount can be based on a bill payment authorization for a paymentamount made by a sender at a payment authorization time. The paymentauthorization can be communicated from sender system 1020 (FIGS. 10-17)in messages 1171 (FIG. 11), 1271 (FIG. 12), 1471 (FIG. 14), 1671 (FIG.16), and/or 1771 (FIG. 17). The sender can be similar or identical tosender 1010 (FIGS. 10-17), who can use sender system 1020 (FIGS. 10-17).The payment authorization time can be the time in which the senderauthorized the bill payment transaction. In several embodiments, thefirst account can be held by the sender, such that the sender is theaccount holder of the first account. In some embodiments, the firstfinancial institution can be different from the second financialinstitution.

In several embodiments, method 2600 additionally can include a block2603 of performing a successful credit for the payment amount to asecond account maintained by the second financial institution to makefunds available in the second account in real-time after the paymentauthorization time. The successful credit can be similar or identical toactivity 1165 (FIGS. 11-12, 14, 16-17) and/or activity 1167 (FIGS.11-12, 14, 16-17). The second account can be similar or identical tobilling account 1061 (FIGS. 10-17) and/or recipient account 1062 (FIGS.10-17). In various embodiments, the sender can be financially liable forthe second account.

In a number of embodiments, method 2600 optionally can include a block2604 of performing a debit for the payment amount from a secondsettlement account maintained by the second financial institution toaccount for the successful credit of the second account maintained bythe second financial institution. The second settlement account can besimilar or identical to receiving participant settlement account 1063(FIGS. 10-17). The debit can be similar or identical to activity 1166(FIGS. 11-12, 14, 16-17).

In a several embodiments, method 2600 further can include, after block2603 or block 2604, a block 2605 of sending a first response from thesecond financial institution indicating the successful credit of thesecond account maintained by the second financial institution to informat least the sender in real-time after the payment authorization time ofthe successful credit of the second account maintained by the secondfinancial institution. The first response can be similar or identical tomessages 1178 (FIG. 11), 1276 (FIG. 12), 1476 (FIG. 14), 1678 (FIG. 16),and/or 1777 (FIG. 17). The sender can be informed by messages 1180 (FIG.11), 1278 (FIG. 12), 1478 (FIG. 14), 1680 (FIG. 16), and/or 1778 (FIG.17).

In some embodiments, the first promise-to-pay message, such as messages1177 (FIG. 11), 1275 (FIG. 12), 1475 (FIG. 14), and/or 1677 (FIG. 16),can be received at the second financial institution from a transactionsystem based on a second promise-to-pay message sent from an applicationservice provider to the transaction system. The transaction system canbe similar or identical to transaction system 1050 (FIGS. 10-17). Thesecond promise-to-pay message can be similar or identical to 1176 (FIG.11), 1274 (FIG. 12), 1474 (FIG. 14), and/or 1676 (FIG. 16). Theapplication service provider can be similar or identical to applicationservice provider 1030 (FIGS. 10-12), application service provider 1330(FIGS. 13-14), and/or application service provider 1530 (FIGS. 15-17).In other embodiments, the first promise-to-pay message, such as message1776 (FIG. 17), can be sent from the application service provider to thesecond financial institution after the application service providerreceives a first debit response from the transaction system indicatingthe successful debit of the first account maintained by the firstfinancial institution. The first debit response can be similar oridentical to message 1775 (FIG. 17).

In some embodiments, the first response, such as messages 1178 (FIG.11), 1276 (FIG. 12), 1476 (FIG. 14), and/or 1678 (FIG. 16) can be sentfrom the second financial institution to the transaction system from thetransaction system, such that a second response is sent from thetransaction system to the application service provider indicating thesuccessful credit of the second account maintained by the secondfinancial institution, and such that the application service providerinforms the sender in real-time after the payment authorization time ofthe successful credit of the second account maintained by the secondfinancial institution. The second response can be similar or identicalto 1179 (FIG. 11), 1277 (FIG. 12), 1477 (FIG. 14), and/or 1679 (FIG.16). In other embodiments, the first response can be sent from thesecond financial institution to the application service provider, suchas in message 1777 (FIG. 17). In some embodiments, the second responsecan be essentially the same as the first response, such as a forward ofthe first response. In other embodiments, the second response caninclude information from the first response, and/or can includeadditional information.

In some embodiments, the application service provider can be a differententity from the first and second financial institutions, such asapplication service provider 1030 (FIGS. 10-12). In other embodiments,the application service provider can be the same entity as the firstfinancial institution, such as application service provider 1330 (FIGS.13-14). In yet other embodiments, the application service provider canbe the same entity as the second financial institution, such asapplication service provider 1530 (FIGS. 15-17).

In a number of embodiments, the second promise-to-pay message, such asmessages 1176 (FIG. 11) and/or 1676 (FIG. 16), can be sent from theapplication service provider to the transaction system after theapplication service provider receives a first debit response from thetransaction system indicating the successful debit of the first accountmaintained by the first financial institution. The first debit responsecan be similar or identical to messages 1175 (FIG. 11) and/or 1675. Inother embodiments, the second promise-to-pay message, such as messages1274 (FIG. 12) and/or 1474 (FIG. 14), can be sent from the applicationservice provider to the transaction system after the application serviceprovider receives a first debit response from the first financialinstitution indicating the successful debit of the first accountmaintained by the first financial institution. The first debit responsecan be similar or identical to messages 1273 (FIG. 12) and/or 1473 (FIG.14).

In some embodiments, the first debit response, such as messages 1175(FIG. 11), 1675 (FIG. 16), and/or 1775 (FIG. 17), received at theapplication service provider can be based on a second debit responsethat was received at the transaction system from the first financialinstitution indicating the successful debit of the first accountmaintained by the first financial institution. The second debit responsecan be similar or identical to messages 1174 (FIG. 11), 1674 (FIG. 16),and/or 1774 (FIG. 17). In some embodiments, the first debit response canbe essentially the same as the second debit response, such as a forwardof the second debit response. In other embodiments, the first debitresponse can include information from the second debit response, and/orcan include additional information.

In many embodiments, the first financial institution can maintain afirst settlement account. The first settlement account can be similar oridentical to sending participant settlement account 1042 (FIGS. 10-17).In a number of embodiments, the first settlement account can be creditedto account for the successful debit of the first account maintained bythe first financial institution, such as in activity 1146 (FIGS. 11-12,14, 16-17).

In several embodiments, the second financial institution can maintain asecond settlement account. The second settlement account can be similaror identical to receiving participant settlement account 1063 (FIGS.10-17). The second settlement account can be debited to account for thesuccessful credit of the second account maintained by the secondfinancial institution, such as in activity 1166 (FIGS. 11-12, 14,16-17).

In many embodiments, funds can be transferred from the first settlementaccount to the second settlement account in a settlement completion. Thesettlement completion can be similar or identical to activities 1191(FIGS. 11-12), 1192 (FIGS. 11-12), and/or 1491 (FIGS. 14, 16-17). Insome embodiments, the settlement completion can be part of a netsettlement as a single item ACH. In other embodiments, the settlementcompletion can be part of a net settlement as part of a batch ACH. Inyet other embodiments, the settlement completion can be part of a netsettlement as part of a wire advice file. In some embodiments, thesuccessful credit of the second account maintained by the secondfinancial institution can involve a hard credit to the second account inreal-time after the payment authorization time. In various embodiments,the settlement completion can involve the funds being transferredthrough a third settlement account of a payment processor. The thirdsettlement account can be similar or identical to payment processorsettlement account 1033 (FIGS. 10-12). In some embodiments, thesettlement completion can occur in real-time after the paymentauthorization time.

Proceeding to the next drawing, FIG. 27 illustrates a block 2601 ofoptional first steps, according to an embodiment. Block 2601 is merelyexemplary and is not limited to the embodiments presented herein. Block2601 can be employed in many different embodiments or examples notspecifically depicted or described herein. In some embodiments, theprocedures, the processes, and/or the activities of block 2601 can beperformed in the order presented. In other embodiments, the procedures,the processes, and/or the activities of block 2601 can be performed inany suitable order. In still other embodiments, one or more of theprocedures, the processes, and/or the activities of block 2601 can becombined or skipped. In many embodiments, block 2601 can be performedbefore the payment authorization time.

Referring to FIG. 27, block 2601 can include a block 2701 of receiving afirst capability inquiry at the second financial institution from thetransaction system to determine whether the second account maintained bythe second financial institution supports real-time paymenttransactions. The first capability inquiry can be similar or identicalto messages 1073 (FIG. 10) and/or 1373 (FIG. 13).

In a number of embodiments, block 2601 also can include a block 2702 ofsending a first capability response from the second financialinstitution to the transaction system indicating whether the secondaccount maintained by the second financial institution supportsreal-time payment transactions, such that the transaction system sends asecond capability response to the application service providerindicating whether the first and second accounts support real-timepayment transactions. The first capability response can be similar oridentical to 1074 (FIG. 10) and/or 1374 (FIG. 15). The second capabilityresponse can be similar or identical to messages 1077 (FIG. 10) and/or1375 (FIG. 15). In some embodiments, the second capability response canbe essentially the same as the first capability response, such as aforward of the first capability response. In other embodiments, thesecond capability response can include information from the firstcapability response, and/or can include additional information.

Turning ahead in the drawings, FIG. 28 illustrates a block diagram ofsystems that can be employed for facilitating a real-time fundsavailability bill-pay transaction, according to an embodiment. Thesystems shown in FIG. 28, which include transaction system 1050, sendingparticipant 1040, receiving participant 1060, and an application serviceprovider, 2830, are merely exemplary and embodiments of the system arenot limited to the embodiments presented herein. The system can beemployed in many different embodiments or examples not specificallydepicted or described herein. In some embodiments, certain elements ormodules of the systems shown in FIG. 28 can perform various procedures,processes, and/or activities. In other embodiments, the procedures,processes, and/or activities can be performed by other suitable elementsor modules of the systems shown in FIG. 28.

In several embodiments, transaction system 1050 can include one or moresystems, such as a communications system 2851, and/or a data system2852.

In many embodiments, communications system 2851 can at least partiallyperform block 1803 (FIG. 18) of receiving a first promise-to-pay messageat a transaction system; block 1805 (FIG. 18) of sending a secondpromise-to-pay message from the transaction system to a second financialinstitution; block 1806 (FIG. 18) of receiving a first response at thetransaction system from the second financial institution indicating asuccessful credit of the second account maintained by the secondfinancial institution; block 1807 (FIG. 18) of storing the firstresponse in the transaction system; block 1808 (FIG. 18) of sending asecond response from the transaction system indicating the successfulcredit of the second account maintained by the second financialinstitution to inform at least the sender in real-time after the paymentauthorization time of the successful credit of the second accountmaintained by the second financial institution; block 1901 (FIG. 19) ofreceiving a first capability inquiry at the transaction system from theapplication service provider; block 1903 (FIG. 19) of sending a secondcapability inquiry from the transaction system to the second financialinstitution to determine whether the second account maintained by thesecond financial institution supports real-time payment transactions;block 1904 (FIG. 19) of receiving a first capability response at thetransaction system from the second financial institution indicatingwhether the second account maintained by the second financialinstitution supports real-time payment transactions; block 1906 (FIG.19) of sending a third capability inquiry from the transaction system tothe first financial institution to determine whether the first accountmaintained by the first financial institution supports real-time paymenttransactions; block 1907 (FIG. 19) of receiving a second capabilityresponse at the transaction system from the first financial institutionindicating whether the first account maintained by the first financialinstitution supports real-time payment transactions; block 1909 (FIG.19) of sending a third capability response from the transaction systemto the application service provider; block 2001 (FIG. 20) of sending adebit message from the transaction system to the first financialinstitution to debit the first account maintained by the first financialinstitution; block 2002 (FIG. 20) of receiving a debit response at thetransaction system from the first financial institution in real-timeafter the payment authorization time; block 2004 (FIG. 20) of sending athird response from the transaction system to the application serviceprovider indicating the successful debit of the first account maintainedby the first financial institution; a block 2101 (FIG. 21) of sending adebit message from a transaction system to a first financial institutionto debit a first account maintained by the first financial institutionbased on a bill payment authorization made by a sender at a paymentauthorization time; block 2102 (FIG. 21) of receiving a debit responseat the transaction system from the first financial institution inreal-time after the payment authorization time; and/or block 2104 (FIG.21) of sending a first response to an application service providerindicating the successful debit of the first account maintained by thefirst financial institution.

In a number of embodiments, data system 2852 can at least partiallyperform block 1804 (FIG. 18) of storing the first promise-to-pay messagein the transaction system; block 1902 (FIG. 19) of storing the firstcapability inquiry in the transaction system; block 1905 (FIG. 19) ofstoring the first capability response in the transaction system; block1908 (FIG. 19) of storing the second capability response in thetransaction system; block 2003 (FIG. 20) of storing the debit responsein the transaction system; and/or block 2103 (FIG. 21) of storing thedebit response in the transaction system.

In several embodiments, sending participant system 1040 can include oneor more systems, such as a communications system 2841, and/or anaccounts system 2842.

In many embodiments, communications system 2841 can at least partiallyperform block 2202 (FIG. 22) of receiving a debit message at a firstfinancial institution to debit a first account maintained by the firstfinancial institution based on a bill payment authorization for apayment amount made by a sender at a payment authorization time; block2205 (FIG. 22) of sending a debit response from the first financialinstitution in real-time after the payment authorization time; block2301 (FIG. 23) of receiving a first capability inquiry at receiving afirst capability inquiry at the first financial institution from thetransaction system to determine whether the first account maintained bythe first financial institution supports real-time payment transactions;and/or block 2302 (FIG. 23) of sending a first capability response fromthe first financial institution to the transaction system indicatingwhether the first account maintained by the first financial institutionsupports real-time payment transactions.

In a number of embodiments, accounts system 2842 can at least partiallyperform activity 1145 (FIGS. 11-12, 14, 16-17); activity 1146 (FIGS.11-12, 14, 16-17); activity 1191 (FIGS. 11-12); activity 1491 (FIGS. 14,16-17); block 2203 (FIG. 22) of performing a successful debit for thepayment amount from the first account maintained by the first financialinstitution in real-time after the payment authorization time; and/orblock 2204 (FIG. 22) of performing a credit for the payment amount to afirst settlement account maintained by the first financial institutionto account for the successful debit of the first account maintained bythe first financial institution.

In several embodiments, receiving participant system 1060 can includeone or more systems, such as a communications system 2861, and/or anaccounts system 2862.

In many embodiments, communications system 2861 can at least partiallyperform block 2602 (FIG. 26) of receiving a first promise-to-pay messageat a second financial institution; block 2605 (FIG. 26) of sending afirst response from the second financial institution indicating thesuccessful credit of the second account maintained by the secondfinancial institution to inform at least the sender in real-time afterthe payment authorization time of the successful credit of the secondaccount maintained by the second financial institution; block 2701 (FIG.27) of receiving a first capability inquiry at the second financialinstitution from the transaction system to determine whether the secondaccount maintained by the second financial institution supportsreal-time payment transactions; and/or block 2702 (FIG. 27) of sending afirst capability response from the second financial institution to thetransaction system indicating whether the second account maintained bythe second financial institution supports real-time paymenttransactions.

In a number of embodiments, accounts system 2862 can at least partiallyperform activity 1165 (FIGS. 11-12, 14, 16-17); activity 1166 (FIGS.11-12, 14, 16-17); activity 1167 (FIGS. 11-12, 14, 16-17); activity 1192(FIGS. 11-12); activity 1491 (FIGS. 14, 16-17); block 2603 (FIG. 26) ofperforming a successful credit for the payment amount to a secondaccount maintained by the second financial institution to make fundsavailable in the second account in real-time after the paymentauthorization time; and/or block 2604 (FIG. 26) of performing a debitfor the payment amount from a second settlement account maintained bythe second financial institution to account for the successful credit ofthe second account maintained by the second financial institution.

In several embodiments, application service provider 2830 can be similaror identical to application service provider 1030 (FIGS. 10-12,application service provider 1330 (FIGS. 13-14), and/or applicationservice provider 1530 (FIGS. 15-17). In a number of embodiments,application service provider 2830 can include one or more systems, suchas a communications system 2831 and/or a payment system 2832. In someembodiments, such as when application service provider 2830 is similaror identical to application service provider 1030 (FIGS. 10-12),application service provider 2830 can include an accounts system 2833.In other embodiments, such as when application service provider 2830 issimilar or identical to application service provider 1330 (FIGS. 13-14)and/or application service provider 1530 (FIGS. 15-17), applicationservice provider 2830 can be devoid of accounts system 2833. In a numberof embodiments, accounts system 2863 can at least partially performactivities 1191 (FIG. 11-12) and/or 1192 (FIGS. 11-12). Similar to otherpayment systems described above, payment system 2832 can be used to payone or more bills and/or other financial obligations.

In many embodiments, communications system 2861 can at least partiallyperform block 2403 (FIG. 24) of receiving a bill payment authorizationfrom the sender through the payment application; block 2404 (FIG. 24) ofsending a first debit message from the application service provider todebit a first account maintained by a first financial institution basedon the bill payment authorization; block 2405 (FIG. 24) of receiving afirst debit response at the application service provider in real-timeafter the payment authorization time; block 2407 (FIG. 24) of sendingthe first promise-to-pay message; block 2408 (FIG. 24) of receiving afirst response at the application service provider indicating asuccessful credit of the second account maintained by the secondfinancial institution; block 2409 (FIG. 24) of sending a notification tothe sender from the application service provider in real-time after thepayment authorization time of the successful credit of the secondaccount maintained by the second financial institution; block 2501 (FIG.25) of sending a first capability inquiry from the application serviceprovider to the transaction system; and/or block 2502 (FIG. 25) ofreceiving a second capability response at the application serviceprovider from the transaction system.

In a number of embodiments, payment system 2832 can at least partiallyperform block 2402 (FIG. 24) of providing a payment application to asender from an application service provider; and/or block 2406 (FIG. 24)of generating a first promise-to-pay message for a second financialinstitution to credit a second account maintained by the secondfinancial institution to make funds available in the second account inreal-time after the payment authorization time.

Although payment real-time funds availability has been described withreference to specific embodiments, it will be understood by thoseskilled in the art that various changes may be made without departingfrom the spirit or scope of the disclosure. Accordingly, the disclosureof embodiments is intended to be illustrative of the scope of thedisclosure and is not intended to be limiting. It is intended that thescope of the disclosure shall be limited only to the extent required bythe appended claims. For example, to one of ordinary skill in the art,it will be readily apparent that any element of FIGS. 1-28 may bemodified, and that the foregoing discussion of certain of theseembodiments does not necessarily represent a complete description of allpossible embodiments. For example, one or more of the procedures,processes, or activities of FIGS. 2-7 and 10-27 may include differentprocedures, processes, and/or activities and be performed by manydifferent modules, in many different orders, and/or one or more of theprocedures, processes, or activities of FIGS. 2-7 and 10-27 may includeone or more of the procedures, processes, or activities of anotherdifferent one of FIGS. 2-7 and 10-27.

Replacement of one or more claimed elements constitutes reconstructionand not repair. Additionally, benefits, other advantages, and solutionsto problems have been described with regard to specific embodiments. Thebenefits, advantages, solutions to problems, and any element or elementsthat may cause any benefit, advantage, or solution to occur or becomemore pronounced, however, are not to be construed as critical, required,or essential features or elements of any or all of the claims, unlesssuch benefits, advantages, solutions, or elements are stated in suchclaim.

Moreover, embodiments and limitations disclosed herein are not dedicatedto the public under the doctrine of dedication if the embodiments and/orlimitations: (1) are not expressly claimed in the claims; and (2) are orare potentially equivalents of express elements and/or limitations inthe claims under the doctrine of equivalents.

What is claimed is:
 1. A system comprising: one or more processingmodules; and one or more non-transitory memory storage modules storingcomputing instructions configured to run on the one or more processingmodules and perform: receiving a first promise-to-pay message at asecond financial institution, the first promise-to-pay message beingbased on a successful debit of a first account maintained by a firstfinancial institution, the successful debit of the first account beingbased on a payment authorization for a payment amount made by a senderat a payment authorization time, and the first account being held by thesender; performing a successful credit for the payment amount to asecond account maintained by the second financial institution to makefunds available in the second account in real-time after the paymentauthorization time, the sender being financially liable for the secondaccount; and sending a first response from the second financialinstitution indicating the successful credit of the second accountmaintained by the second financial institution to inform at least thesender in real-time after the payment authorization time of thesuccessful credit of the second account maintained by the secondfinancial institution, wherein: the first financial institution isdifferent from the second financial institution.
 2. The system of claim1, wherein the computing instructions are further configured to perform,after receiving the first promise-to-pay message: performing a debit forthe payment amount from a second settlement account maintained by thesecond financial institution to account for the successful credit of thesecond account maintained by the second financial institution.
 3. Thesystem of claim 1, wherein: the first promise-to-pay message is receivedat the second financial institution from a transaction system based on asecond promise-to-pay message sent from an application service providerto the transaction system; and the first response is sent from thesecond financial institution to the transaction system, such that asecond response is sent from the transaction system to the applicationservice provider indicating the successful credit of the second accountmaintained by the second financial institution, and such that theapplication service provider informs the sender in real-time after thepayment authorization time of the successful credit of the secondaccount maintained by the second financial institution.
 4. The system ofclaim 3, wherein: the application service provider is a different entityfrom the first and second financial institutions.
 5. The system of claim4, wherein the computing instructions are further configured to perform,before the payment authorization time: receiving a first capabilityinquiry at the second financial institution from the transaction systemto determine whether the second account maintained by the secondfinancial institution supports real-time payment transactions; andsending a first capability response from the second financialinstitution to the transaction system indicating whether the secondaccount maintained by the second financial institution supports thereal-time payment transactions, such that the transaction system sends asecond capability response to the application service providerindicating whether the first and second accounts support the real-timepayment transactions.
 6. The system of claim 4, wherein: the secondpromise-to-pay message is sent from the application service provider tothe transaction system after the application service provider receives afirst debit response from the transaction system indicating thesuccessful debit of the first account maintained by the first financialinstitution; and the first debit response received at the applicationservice provider is based on a second debit response that was receivedat the transaction system from the first financial institutionindicating the successful debit of the first account maintained by thefirst financial institution.
 7. The system of claim 4, wherein thesecond promise-to-pay message is sent from the application serviceprovider to the transaction system after the application serviceprovider receives a first debit response from the first financialinstitution indicating the successful debit of the first accountmaintained by the first financial institution.
 8. The system of claim 3,wherein: the application service provider is the same entity as thefirst financial institution.
 9. The system of claim 8, wherein thecomputing instructions are further configured to perform, before thepayment authorization time: receiving a first capability inquiry at thesecond financial institution from the transaction system to determinewhether the second account maintained by the second financialinstitution supports real-time payment transactions; and sending a firstcapability response from the second financial institution to thetransaction system indicating whether the second account maintained bythe second financial institution supports the real-time paymenttransactions, such that the transaction system sends a second capabilityresponse to the application service provider indicating whether thesecond account supports the real-time payment transactions.
 10. Thesystem of claim 8, wherein the second promise-to-pay message is sentfrom the application service provider to the transaction system afterthe application service provider receives a first debit response fromthe first financial institution indicating the successful debit of thefirst account maintained by the first financial institution.
 11. Thesystem of claim 3, wherein: the application service provider is the sameentity as the second financial institution.
 12. The system of claim 11,wherein: the second promise-to-pay message is sent from the applicationservice provider to the transaction system after the application serviceprovider receives a first debit response from the transaction systemindicating the successful debit of the first account maintained by thefirst financial institution; and the first debit response received atthe application service provider is based on a second debit responsethat was received at the transaction system from the first financialinstitution indicating the successful debit of the first accountmaintained by the first financial institution.
 13. The system of claim1, wherein: the first promise-to-pay message is received at the secondfinancial institution from an application service provider; theapplication service provider is the same entity as the second financialinstitution; the first promise-to-pay message is sent from theapplication service provider to the second financial institution afterthe application service provider receives a first debit response fromthe transaction system indicating the successful debit of the firstaccount maintained by the first financial institution; and the firstdebit response received at the application service provider is based ona second debit response that was received at the transaction system fromthe first financial institution indicating the successful debit of thefirst account maintained by the first financial institution.
 14. Thesystem of claim 1, wherein: the first financial institution maintains afirst settlement account; the first settlement account is credited toaccount for the successful debit of the first account maintained by thefirst financial institution; the second financial institution maintainsa second settlement account; the second settlement account is debited toaccount for the successful credit of the second account maintained bythe second financial institution; and funds are transferred from thefirst settlement account to the second settlement account in asettlement completion.
 15. The system of claim 14, wherein: thesettlement completion is part of a net settlement as a single item ACH.16. The system of claim 14, wherein: the settlement completion is partof a net settlement as part of a batch ACH.
 17. The system of claim 14,wherein: the settlement completion is part of a net settlement as partof a wire advice file.
 18. The system of claim 14, wherein: thesuccessful credit of the second account maintained by the secondfinancial institution involves a hard credit to the second account inreal-time after the payment authorization time.
 19. The system of claim14, wherein: the settlement completion involves the funds beingtransferred through a third settlement account of a payment processor.20. The system of claim 14, wherein: the settlement completion occurs inreal-time after the payment authorization time.
 21. A method beingimplemented via execution of computer instructions configured to run atone or more processing modules and configured to be stored at one ormore non-transitory memory storage modules, the method comprising:receiving a first promise-to-pay message at a second financialinstitution, the first promise-to-pay message being based on asuccessful debit of a first account maintained by a first financialinstitution, the successful debit of the first account being based on apayment authorization for a payment amount made by a sender at a paymentauthorization time, and the first account being held by the sender;performing a successful credit for the payment amount to a secondaccount maintained by the second financial institution to make fundsavailable in the second account in real-time after the paymentauthorization time, the sender being financially liable for the secondaccount; and sending a first response from the second financialinstitution indicating the successful credit of the second accountmaintained by the second financial institution to inform at least thesender in real-time after the payment authorization time of thesuccessful credit of the second account maintained by the secondfinancial institution, wherein: the first financial institution isdifferent from the second financial institution.
 22. The method of claim21, wherein the computing instructions are further configured toperform, after receiving the first promise-to-pay message: performing adebit for the payment amount from a second settlement account maintainedby the second financial institution to account for the successful creditof the second account maintained by the second financial institution.23. The method of claim 21, wherein: the first promise-to-pay message isreceived at the second financial institution from a transaction systembased on a second promise-to-pay message sent from an applicationservice provider to the transaction system; and the first response issent from the second financial institution to the transaction system,such that a second response is sent from the transaction system to theapplication service provider indicating the successful credit of thesecond account maintained by the second financial institution, and suchthat the application service provider informs the sender in real-timeafter the payment authorization time of the successful credit of thesecond account maintained by the second financial institution.
 24. Themethod of claim 23, wherein: the application service provider is adifferent entity from the first and second financial institutions. 25.The method of claim 24, wherein the computing instructions are furtherconfigured to perform, before the payment authorization time: receivinga first capability inquiry at the second financial institution from thetransaction system to determine whether the second account maintained bythe second financial institution supports real-time paymenttransactions; and sending a first capability response from the secondfinancial institution to the transaction system indicating whether thesecond account maintained by the second financial institution supportsthe real-time payment transactions, such that the transaction systemsends a second capability response to the application service providerindicating whether the first and second accounts support the real-timepayment transactions.
 26. The method of claim 24, wherein: the secondpromise-to-pay message is sent from the application service provider tothe transaction system after the application service provider receives afirst debit response from the transaction system indicating thesuccessful debit of the first account maintained by the first financialinstitution; and the first debit response received at the applicationservice provider is based on a second debit response that was receivedat the transaction system from the first financial institutionindicating the successful debit of the first account maintained by thefirst financial institution.
 27. The method of claim 24, wherein thesecond promise-to-pay message is sent from the application serviceprovider to the transaction system after the application serviceprovider receives a first debit response from the first financialinstitution indicating the successful debit of the first accountmaintained by the first financial institution.
 28. The method of claim23, wherein: the application service provider is the same entity as thefirst financial institution.
 29. The method of claim 28, wherein thecomputing instructions are further configured to perform, before thepayment authorization time: receiving a first capability inquiry at thesecond financial institution from the transaction system to determinewhether the second account maintained by the second financialinstitution supports real-time payment transactions; and sending a firstcapability response from the second financial institution to thetransaction system indicating whether the second account maintained bythe second financial institution supports the real-time paymenttransactions, such that the transaction system sends a second capabilityresponse to the application service provider indicating whether thesecond account supports the real-time payment transactions.
 30. Themethod of claim 28, wherein the second promise-to-pay message is sentfrom the application service provider to the transaction system afterthe application service provider receives a first debit response fromthe first financial institution indicating the successful debit of thefirst account maintained by the first financial institution.
 31. Themethod of claim 23, wherein: the application service provider is thesame entity as the second financial institution.
 32. The method of claim31, wherein: the second promise-to-pay message is sent from theapplication service provider to the transaction system after theapplication service provider receives a first debit response from thetransaction system indicating the successful debit of the first accountmaintained by the first financial institution; and the first debitresponse received at the application service provider is based on asecond debit response that was received at the transaction system fromthe first financial institution indicating the successful debit of thefirst account maintained by the first financial institution.
 33. Themethod of claim 21, wherein: the first promise-to-pay message isreceived at the second financial institution from an application serviceprovider; the application service provider is the same entity as thesecond financial institution; the first response is sent from the secondfinancial institution to the application service provider; the firstpromise-to-pay message is sent from the application service provider tothe second financial institution after the application service providerreceives a first debit response from the transaction system indicatingthe successful debit of the first account maintained by the firstfinancial institution; and the first debit response received at theapplication service provider is based on a second debit response thatwas received at the transaction system from the first financialinstitution indicating the successful debit of the first accountmaintained by the first financial institution.
 34. The method of claim21, wherein: the first financial institution maintains a firstsettlement account; the first settlement account is credited to accountfor the successful debit of the first account maintained by the firstfinancial institution; the second financial institution maintains asecond settlement account; the second settlement account is debited toaccount for the successful credit of the second account maintained bythe second financial institution; and funds are transferred from thefirst settlement account to the second settlement account in asettlement completion.
 35. The method of claim 34, wherein: thesettlement completion is part of a net settlement as a single item ACH.36. The method of claim 34, wherein: the settlement completion is partof a net settlement as part of a batch ACH.
 37. The method of claim 34,wherein: the settlement completion is part of a net settlement as partof a wire advice file.
 38. The method of claim 34, wherein: thesuccessful credit of the second account maintained by the secondfinancial institution involves a hard credit to the second account inreal-time after the payment authorization time.
 39. The method of claim34, wherein: the settlement completion involves the funds beingtransferred through a third settlement account of a payment processor.40. The method of claim 34, wherein: the settlement completion occurs inreal-time after the payment authorization time.